Postfix record member access expression

[leewei05]

Changes for types

• Introduce a new struct Field for storing both id and Type for record members.
• Introduce a new class RecordType for sharing common methods for struct and union.

AST

• Introduce a new AST node RecordMemExprNode for postfix record member access expression.

Other

• Update dump info for InitExprNode.

P.S: I had added additional typecheck tests, but I haven't implemented any code generation for record declaration, so it will throw error src/qbe_ir_generator.cpp:108: int {anonymous}::PrevExprNumRecorder::NumOfPrevExpr(): Assertion num_of_prev_expr_ != kNoRecord. I can add additional expression tests after implementing code generation.

I can start implementing code generation for struct and union after this PR. 😄

[Lai-YT]

Once again, thank you for supporting the record types. I submitted some changes that I believe can improve the PR even further.

Additionally, if a struct and a union share the same name, such as struct SomeName and union SomeName, would there be a collision in the type table?

[leewei05]

Additionally, if a struct and a union share the same name, such as struct SomeName and union SomeName, would there be a collision in the type table?

Right! I haven't thought about that case. I think it needs an extra type check for LoopUpType.

[Lai-YT]

Additionally, if a struct and a union share the same name, such as struct SomeName and union SomeName, would there be a collision in the type table?

Right! I haven't thought about that case. I think it needs an extra type check for LoopUpType.

Or maybe we include the "struct " and "union " as the prefix of the id? XD

[leewei05]

Additionally, if a struct and a union share the same name, such as struct SomeName and union SomeName, would there be a collision in the type table?

Right! I haven't thought about that case. I think it needs an extra type check for LoopUpType.

Or maybe we include the "struct " and "union " as the prefix of the id? XD

Great suggestion! Let me try to implement with this approach.

[Lai-YT]

LGTM! We're moving on to code generation!! Oh yay 🎉