Will this break in the future? #1257
Unanswered
karl-police
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Short concept, also this is without
DebugLuauDeferredConstraintResolution
, later below, I'll mention when I enable it.This is done automatically.
Now, I will demonstrate a problem, of autocompletion.
And now I will demonstrate dynamic 2 solutions.
Solution 1:
And what I just discovered, is Solution 2.
Short explanation:
These small mini-hacks, create this uncreatable type of table, that just allows autocompletion. Perhaps this table has a name, something with mutable and unmutable. Thing is, in the current scope, it works.
I know that
DebugLuauDeferredConstraintResolution
currently breaks it, but it's a WIP, yet concerning. Finding these workarounds are tricky.With DeferredConstraint:
All of it is broken.
However, there's something really strange. I will highlight it like so.
Something really strange
This is with
DebugLuauDeferredConstraintResolution
, and all I did was to put a Generic Variable that is purely unused anywhere. This could be a bug, somewhere.We could go back to Issue #1239
Where
:Get()
only shows up in the autocomplete if all parameters are not a free variable.But it also happens through Generic Types, that are unused.
It's very strange.
Beta Was this translation helpful? Give feedback.
All reactions