Skip to content
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

Don't forget to update f_id_of_upvalue #522

Merged
merged 1 commit into from
Apr 28, 2022
Merged

Don't forget to update f_id_of_upvalue #522

merged 1 commit into from
Apr 28, 2022

Conversation

hugomg
Copy link
Member

@hugomg hugomg commented Apr 22, 2022

Fixes #508. In the long term, we should look for ways to get rid of the f_id_of_upvalue altogether. If we had an analysis pass that computed it, we wouldn't need to maintain and update it across other compilation passes.

@ewmailing, could you please check if this fixes the bug on your end? Sorry it took so long, and thanks again for reporting it!

Fixes #508. In the long term, we should look for ways to get rid of the f_id_of_upvalue altogether.
If we had an analysis pass that computed it, we wouldn't need to maintain and update it across other
compilation passes.
@hugomg hugomg merged commit 58374b6 into master Apr 28, 2022
@hugomg hugomg deleted the bug-508 branch April 28, 2022 01:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Parse bug: sometimes fails on valid code (triggers assertion failure in coder.lua)
1 participant