[refactor] [ir] Remove load_if_ptr and move pointer dereferencing to frontend-to-IR passes #4104
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related issue = #3982
Frontend IR is supposed to be a language higher level than ChiIR, but unnecessary details of pointer manipulation (i.e.
LoadExpression
s) are still present. Although users won't be able to notice this in python, that was achieved by spreadingload_if_ptr
across literally the whole frontend. What's worse, for any expressione
,LoadExpression(e)
has the same types ase
(that is, value type = pointer type), making bugs extremely easy to sneak in.This PR removed
LoadExpression
s andload_if_ptr
so that pointers are not visible in frontend. Instead, pointer dereferencing is done at frontend-to-IR passes (Expr::flatten()
andirpass::lower_ast()
) wtih helper functionsflatten_lvalue()
(gives pointers) andflatten_rvalue()
(gives values).