Skip to content

Conversation

@karl-police
Copy link
Contributor

@karl-police karl-police commented Aug 3, 2025

Fixes #1946

--!strict
a = a
function a:test() end

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 FFlagLuauFixPrepopulateGlobalOnSameGlobal

If there's a
a = a the 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

image

 

Why are rhs values even going into a collection that is named globalScope->lvalueTypes though?

Were rhs values ever intended to be processed by the visitor?

@karl-police karl-police changed the title Fix blocked-type leak when defining global with the same global name Fix blocked-type leak when assigning global with the same global name Aug 3, 2025
@karl-police
Copy link
Contributor Author

I probably have to re-order the if statement, I noticed it can be made a bit better. But I will leave it like this for now until I get opinions about this fix. 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

global = global HasProp blocked-type leak

1 participant