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.