On 3/17/22 07:25, matheus wrote:
> Any chance this will be available for watch later?
As always, it wasn't in presentation style; rather, my pointing at what
is possible in source code. I will write something up and make example
code available.
Ali
On Fri, Mar 18, 2022 at 09:30:57PM +, Adam Ruppe via Digitalmars-d-announce
wrote:
[...]
> One approach you might consider is a hybrid too, where you have the
> big struct you build out of the individual udas.
>
> So you work on the big one but you do getBig!decl and it loops through
> the
On Friday, 18 March 2022 at 18:21:46 UTC, Anonymouse wrote:
I use UDAs extensively in my project and I've historically been
doing the multiple-UDA approach you describe. Upon seeing
argparse a few months back I started rewriting it to use a
single UDA, and I found it allowed for a simpler
On Fri, Mar 18, 2022 at 06:21:46PM +, Anonymouse via Digitalmars-d-announce
wrote:
> On Thursday, 17 March 2022 at 19:07:28 UTC, H. S. Teoh wrote:
> > Using independent, orthogonal UDAs may make option specification
> > using your module easier to read. For example, from your docs:
[...]
> >
On Friday, 18 March 2022 at 19:09:27 UTC, Adam D Ruppe wrote:
On Friday, 18 March 2022 at 18:21:46 UTC, Anonymouse wrote:
One drawback is documentation; adrdox does *not* like these
kinds of UDAs.
It is on my list to run big UDAs through the auto-formatter at
some point pretty soon to help
On Friday, 18 March 2022 at 18:21:46 UTC, Anonymouse wrote:
One drawback is documentation; adrdox does *not* like these
kinds of UDAs.
It is on my list to run big UDAs through the auto-formatter at
some point pretty soon to help with this. I just have a big work
project I'm wrapping up
On Thursday, 17 March 2022 at 19:07:28 UTC, H. S. Teoh wrote:
Using independent, orthogonal UDAs may make option
specification using your module easier to read. For example,
from your docs:
struct T {
@(NamedArgument
.PreValidation!((string s) { return s.length > 1
