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
The mere presence of a type in a project should not expose that type to every file i.e. types should not be global.
Luanalysis should (recursivelyEDIT: Recursively pulling in is a bad idea, don't do that) pull in types when it sees a require. Additionally, we should provide some mechanism to allow consumers to avoid type name collisions.
The mere presence of a type in a project should not expose that type to every file i.e. types should not be global.
Luanalysis should (
recursivelyEDIT: Recursively pulling in is a bad idea, don't do that) pull in types when it sees arequire
. Additionally, we should provide some mechanism to allow consumers to avoid type name collisions.e.g.
Just a hypothetical solution, other languages allow individual types to be renamed. The above is fairly low friction though.
Additionally, we may want to define types that we never export to consumers i.e. consider adding
local
types like:---@local alias Builder fun(): void
The text was updated successfully, but these errors were encountered: