Named arguments via struct initialization in functions

ZombineDev via Digitalmars-d digitalmars-d at puremagic.com
Thu Mar 10 11:36:05 PST 2016


On Monday, 7 March 2016 at 18:21:24 UTC, Meta wrote:
> On Monday, 7 March 2016 at 10:40:15 UTC, ZombineDev wrote:
>> Which I don't think will cause ambiguity with delegates:
>> auto tuple3 = { getInt() }; tuple
>> auto tuple3 = { getInt(); }; lambda
>
> Unfortunately this will not work. There was a tuple proposal 
> sometime back in 2012 or 2013. I can't remember the exact 
> reason, but somebody came up with a case where it can be 
> ambiguous as to whether it's a tuple or a delegate.

Can you find the exact case? I'm really interested in getting 
proper tuple syntax support and I think that's important to cover 
all the possible cases before can agree on something and move 
towards implementing it.


More information about the Digitalmars-d mailing list