Haxe 4.3 documentation TODO

[Simn]

• defaults for type parameters (Default type parameters haxe#10518)
• support abstract keyword to reference the abstract (Abstract abstract haxe#10513)
• support static var at expression-level (Support static for locals haxe#10555)
• support ?. safe navigation operator (Safe navigation operator haxe#10561)
• added ?? null coalescing operator (Null coalescing operator haxe#10428)
• add -w compiler option to configure warnings (Add -w haxe#10612)
• support custom metadata and defines (Custom metadata and defines (documentation, completion) haxe#10858)

[EliteMasterEric]

I ended up writing this blog post which covers all of these features: https://www.elitemastereric.com/Haxe-430/

I sadly don't have the time to help out by copying parts of this over and cleaning them up (this post alone took several hours and I haven't made dinner), but anyone working on improving the official documentation can feel free to copy and use this post or portions of it in there.

[RblSb]

You can add link to https://haxe.org/download/, update already on this page

[Simn]

That is great content, thank you! I'll see to it that we add a link to it from the release notes.

Regarding -w, I decided to not use any numeric codes because I don't see any reason to do so. Every warning has its unique identifier, which is printed alongside the warning. So you can always just -w -WIdentifier to immediately deal with it. We will probably generate a list from this JSON source: https://github.com/HaxeFoundation/haxe/blob/development/src-json/warning.json

[kLabz]

Thank you for your blog post, that will help the community while we work on writing (and deploying...) the documentation about new things, "breaking fixes" , etc.

While I go through all that to work on new pages, I can point out things that are a bit incorrect if you want to edit your post. From what I remember from my first "quick" read it's mostly correct, so there won't be much. Maybe you want to fix that "type safety" at the end that is supposed to be "null safety" , if that's not fixed already.

[kLabz]

• Update macro reification page to add something about the 4.3 change too?