Expression evaluation order

[monarch_dodra]

On Saturday, 15 June 2013 at 17:50:39 UTC, Walter Bright wrote:
> On 6/13/2013 11:14 PM, monarch_dodra wrote:
>> 3) specifically unspecified
>>   3.5) error when compiler sees ambiguity
>>
>> I'm personally in favor of 3, with some 3.5 as a warning.
>
> Having a warning for that is "boy who cried wolf", as most 
> functions have side effects and any expression like:
>
>    f() + g()
>
> would generate such a warning.

Well, why would that throw a warning?

I didn't mean expressions that *could* raise an ambiguity, but 
when the compiler *catches* that there *will* be ambiguity.