Enhancement: add "|none" to each named argument of each code section method

[dumblob]

Currently it's impossible to simply express, that one doesn't want to mention an attribute in some cases, but does want to in other cases anchor(_class=%c ? c : none){ .... This might be easily achieved by enhancing the interface of each code section method argument with |none with the following semantics:

anchor(href=none){} -> <a></a>
anchor(href=5){} -> <a href="5"></a>

none could be also used with the same semantics for return values of code section methods:

anchor { "" } -> <a></a>
anchor {} -> anchor { none } ->

But this use for whole tags seems slightly odd, even though it's handy.

[Night-walker]

You proposal is based on an invalid assumption. You can't write c? a : b if the types of a and b don't match.

[Night-walker]

It would make the prototypes too complicated. Try to use tuples to make attribute lists.

[dumblob]

Try to use tuples to make attribute lists.

dao -e 'load web.html import html; fragment { x = 5 == 5 ? (@T)(href="yes",_class="sth") : (@T)(href="no",); anchor(x, ...) { "A" } }

Currently impossible/difficult due to bug daokoder/dao#507 .

[dumblob]

Bug daokoder/dao#507 has been fixed, but the example doesn't work anyway. What did you mean by Try to use tuples to make attribute lists.?

[dumblob]

routine r(...: tuple<enum<x>, int>|tuple<enum<y>, string> as args) { io.writeln(args) }
t = 0 == 0 ? (($x,9),) : (($y, "c"), ($x,3))
r(t, ...)

This also doesn't work (of course, because tuple types are not matching), even though it can be solved pretty easily with casting to tuple<...>. But the issue with this is, that it's really cumbersome and unreadable.

[Night-walker]

What did you mean by Try to use tuples to make attribute lists.?

Only that you can attempt to construct tuples of arguments based on your conditions and then pass them to tag functions.