New LM Style for Type Definitions (idea roundup)

[andrew-johnson-4]

There have been several problems and inefficiencies with current type definitions with LM Style structs. The entire codepaths from back to frontend will be replaced during the LM to LSTS rewrite, so this is the perfect time to rearchitect anything.

Proposed New Features:

• tags are elided if there is only one case
• fields can be attached to the type directly, outside of all cases
• LM Style definitions should accept all C Style definitions (packing / alignment / nesting)
• get rid of "aliases" in favor of direct field declarations
  • aliases were originally a way of minimizes resource usage in the compiler
  • the compiler can efficiently handle this stuff now, so it should not be a problem
• mangle field names to be human readable after demangling
• inline implements in type definition

Existing Tickets:

• Remove tag from tagged unions as appropriate. #1047

Anything else missing?

[alex-s168]

seems like a good idea

I also want inline implements, in the definition