Add -w

[Simn]

I also want to add @:haxe.warning, but this isn't so easy because we probably have to persist this information in the types and fields so that all post-processing can check it. Some architectural challenges here.

Syntax follows OCaml's somewhat:

-w +123 # enable
-w -123 # disable
-w +123+124-125 # multiple
-w +123...127 # range

We'll have to sort out the codes before the next release because we shouldn't really change these.

[Aurel300]

Might be good to "reserve" more than 100 per category. Also since you are doing this: error codes are useful too, they make it really easy to uniquely identify an error and document it in a manual.

[Simn]

Also since you are doing this: error codes are useful too, they make it really easy to uniquely identify an error and document it in a manual.

I agree. I actually wouldn't mind doing the dumb labor required for that, but somehow I'm always very reluctant to assign unique numbers to things... I suppose I'll have to get over that at some point!

[Simn]

Also, I don't know why I'm talking about persisting anything. The information is already in the metadata and can just be extracted from there. So the only challenge is making sure that all warning functions become somewhat contextual so that they can check their current class/field. That should be doable.

[Simn]

Alright, if anyone wants to design these codes, you're very welcome to do so! Otherwise I'll merge this next week and we'll deal with that a bit later (but before the next release).