-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pointer mutability information after type-checking is not trustworthy #190
Comments
Starting from "After variable renaming to remove copies", the |
(sry, didn't want to close) |
vbgl
changed the title
#190
Pointer mutability information after type-checking is not trustworthy
Jun 29, 2022
vbgl
added a commit
that referenced
this issue
Sep 1, 2022
bgregoir
pushed a commit
that referenced
this issue
Sep 1, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Keeping track of the writability (
const
/mut
) property of variables during the compilation passes is difficult and probably not needed. When compiling this example, we can notice that after inlining and removal of “renaming” assignments, variablesarg
andro
get merged and the single variable that represent both has wrong mutability. Unfortunately, “stack allocation” trusts this mutability information and wrongly rejects the program.The text was updated successfully, but these errors were encountered: