Fix blocked-type leak when assigning global with the same global name #1942
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.
Fixes #1946
I was trying to find what would be the correct fix, that much, that it made me mad, because there's no way for me to figure it out, unless I learn everything that is contained inside this repository, or something and understand it.
This adds
FFlagLuauFixPrepopulateGlobalOnSameGlobalIf there's a
a = athe rhs gets banned from the prepopulator :). 🤷Maybe my idea is stupid or maybe not. Lemme know, thanks.
The reason on why the prepopulator is because I set breakpoints and it's something that starts happening in the ConstraintGenerator.
I made comparisons with a bugged vs. non-bugged one, for instance
Why are rhs values even going into a collection that is named
globalScope->lvalueTypesthough?Were rhs values ever intended to be processed by the visitor?