We have LARGE Luau types and sometimes there is a simple yet very hard to diagnose type-mismatch, such as this screenshot:
The error fortunately was located in this one, but sometimes it’s hard to read these and see the difference. The main issue is that it hides so much, it’s hard to really see the difference. I think a good potential solution for this kind of error would be doing a diff on the types and showing only the differences in some manner.
Anyway, thank you!
Feelin’ like trying to diagnose C++ template errors
For the time being, you can use Script Analysis, it makes the problem somewhat bearable.
But yeah, this do be annoying when messing with deeply-nested generic types
Thanks for the report; We’ll follow up when we have an update for you.
A connected issue to this is that when you are hovering an error it disappears after 10 seconds LOL
Hello!
Sorry for the late response and thanks for the report!
We’ve been hard at work on a refresh of the Luau type inference engine. It should be smarter about this.
The new type solver is still a work-in-progress, but it is currently in public beta and you can try it out if you like. You can read about it here.
I’ve been trying to use the new type solver, but it’s not ready for our projects yet. Waiting for the current round of changes to hit to see if there are any improvements. I tried using it the other day, but I had over 10,000 warnings in my project. I love the features and am excited for it to get to production level! Thanks!
