Allow (some) keywords as field names / var names about haxe-evolution HOT 4 CLOSED

I guess this is a question of context-specific keywords which should be possible, and even useful, but not I'm sure what long-term consequences that's gonna have. (e.g. if we allow enum as an identifier, i'll be harder to introduce local enum type declaration if we'll ever want it).

from haxe-evolution.

In that case, what if we only allow field access, so leaving import * and var as-is? In other words, MyClass.default(...) would work, while import MyClass.* + default(...) would result in the usual parse error.

Btw, i want to mention that among all keywords, I think the most "wanted" one would be default and in, which I encounter most in extern APIs and external data (e.g. json)

from haxe-evolution.

This is not worth it. It would complicate the parser for no real benefit other than a mildly nicer to read field access in some rare cases. There's already some inconsistency with the macro and extern keywords being allowed in package names, but that doesn't mean that we have to make it worse.

I'm pretty sure this would also annoy many IDEs.

from haxe-evolution.

My concrete proposal summary:

from haxe-evolution.