On 3/24/14, 5:18 AM, "Marc Schütz" <[email protected]>" wrote:
On Monday, 24 March 2014 at 04:00:14 UTC, Andrei Alexandrescu wrote:
On 3/23/14, 8:30 PM, bearophile wrote:
How is this more limited change affecting possible future syntax usage
of commas for tuples? :-)
The change has an eye to that. Disallowing the use of the return value
offers us the future possibility of redefining it. -- Andrei
This is nice, although I guess it will make parsing harder. It probably
means that the distinction between "," as operator and tuple element
separator will be context-dependent.
No, parsing stays the same. You can think of comma returning a tuple.
But for now we're forcing that tuple to never be used, so as to not
change code semantics.
Andrei
