New luau typesolver thinks that parent of the instance is a strict value and its type cannot be changed


image

Yeah im not even gonna explain it, it expects modulescript as a parent…

Expected behavior
State that direct references to static instances in the explorer or clones of them need to have a .Parent field that accepts a new index of type Instance? and not a type strict to the direct reference’s Parent type

3 Likes

atp just remove the type solver the new and old ones are trash and most likely will just annoy people. At one point in time the new typesolver was linting the top of every script orange for no reason and i just had to cope with --!nocheck; its so terrible.

1 Like

Disable it per-game in Workspace properties if you dislike it so much, many people use the type system to write type-safe code.

1 Like

just use typescript bro
just use typescript

im not using typescript just to use typescript and run around and tell people that i use typescript :wilted_flower:

1 Like

Please adjust the title of your report to actually describe the issue, this is not appropriate conduct for reporting a bug. I can appreciate that bugs are frustrating, but we can’t reasonably track and fix them when the mechanism of reporting them is sarcasm. We, of course, will not be removing the type system as a product just because you don’t like it, but you’re welcome to set the default mode to nocheck and disable all the type inference powered editor features, including autocomplete, if you truly want nothing to do with it.

9 Likes

Proposed fix for this bug is:
The state that direct references to static instances in the explorer or clones of them need to have a .Parent field that accepts a new index of type Instance? and not a type strict to the direct reference’s Parent type

You don’t need to propose how to fix bugs, but again, please adjust the title of this ticket to describe the bug. Without an actual title, your issue is likely to be missed.

1 Like

adjusted the title‎ ‎ ‎ ‎ ‎ ‎ ‎

Fixed woo-hoo! The type of Instance.Parent will remain a nullable instance…
Edit: Now waiting for table generics, lol.

Sorry for the delay in circling back to this issue. It has been resolved for a while now, as reported by @Someoneslamp, so I’m going to close out the issue. Please feel welcome to report any further issues you run into, but remember to focus on the actual issue and provide a reproducing example when you do!

2 Likes

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.