You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I named middle layer objects "Meta" because originally they were additional information to AST objects, but over time they grew bigger and now they are not only "additional" stuff. Actually they are main objects that the code generator is directly dealing with.
New names can be "IRXxx" or "MIRXxxx"
The text was updated successfully, but these errors were encountered:
This kind of massive renaming would cause a large amount of conflicts, so we should take care of other big ongoing
branches.
DQNEO
changed the title
Rename Meta* types and funcs to IR or MIR names
Rename Meta* objects (types, funcs and vars) to IR or MIR names
Jul 18, 2023
DQNEO
changed the title
Rename Meta* objects (types, funcs and vars) to IR or MIR names
main.go: Rename Meta* objects (types, funcs and vars) to IR or MIR names
Jul 18, 2023
I named middle layer objects "Meta" because originally they were additional information to AST objects, but over time they grew bigger and now they are not only "additional" stuff. Actually they are main objects that the code generator is directly dealing with.
New names can be "IRXxx" or "MIRXxxx"
The text was updated successfully, but these errors were encountered: