You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if this is intended or not, but the linter will not be able to detect the unknownGlobal or unknownGlobal2 variables without being declared both in strict and non-strict mode. This only applies when they are used in conditions using the "==" and "~=" operators.
* Fix a bug where reading a property from an unsealed table caused
inference to improperly infer the existence of that property.
* Fix#827
We have also made a lot of progress on the new solver and the JIT. Both
projects are still in the process of being built out. Neither are ready
for general use yet.
We are mostly working to tighten up how the new solver handles
refinements and updates to unsealed tables to bring it up to the same
level as the old solver.
---------
Co-authored-by: Arseny Kapoulkine <[email protected]>
Co-authored-by: Vyacheslav Egorov <[email protected]>
Not sure if this is intended or not, but the linter will not be able to detect the
unknownGlobal
orunknownGlobal2
variables without being declared both in strict and non-strict mode. This only applies when they are used in conditions using the "==" and "~=" operators.However, localizing the functions at the beginning of the script or typecasting the parameter with any type will resolve the issue.
The text was updated successfully, but these errors were encountered: