Road Towards Stable Syntax

[PeyTy]

Is your feature request related to a real-world problem?

Next-Version Syntax Reference: https://github.com/hexalang/Hexa/blob/kawaii/docs/reference.md#hexa-syntax-reference-draft

Okay, I made like 9999 experiments and now want to make it clear what should happen before Hexa can be considered a mostly syntactically backwards-compatible language:

• Replace declare T = T type alias with a more common syntax type T = T (if we just continue use aliases only for types this way, as older ideas of using them as macro-templates is no more considered)
• Enum patterns to become name-based instead of position-based + enum E : T now enum E T
• Advanced pattern matching + exhaustive switch
• Settle hexa.json schema
• Floats (fixed, 16-bit, etc)
• Integers (BE, defaults, complex, etc)
• Doc comments /// format
• JSON-compatibility (copy-paste JSON into .hexa, requires : and , as operators) + preserve js feel
• Modularity version 3
• Null-unwrapping operator (!) + re-enable nullability checks
• Better casting operator (as)
• Ternaries that play well with ?.
• JSX
• Raw strings
• Meta-methods
• Finalize package manager format

---

Features that would be set in stone will go into Long-Term Support tests at Hexa/kawaii/test

Agreements

• I agree to follow this project's Contributing Guidelines
• I agree to follow this project's Code of Conduct