How to improve TSL support

[huntercaron]

I came across this callout in this SB codes article for learning TSL about there being "hundreds" of TSL type errors. Which can be seen through many ts-ignore comments in his code examples.

I am curious if this seems accurate? and if the reason is correct? In my limited experience so far, there does seem to be plenty of errors.

Would the best approach to help here be to create issues and fixes as I run into them or is a more systematic solve possible?

[Methuselah96]

The TSL types are indeed immature. I'm (slowly) working on improving them, but it takes a lot of effort since some of the types are not straightforward. I would create issues and fixes as your run into them.

[Methuselah96]

Is there a way to access the final code from the SB code articles? That would be the most helpful, then I could just work through the errors directly.

[huntercaron]

thanks for the quick reply, makes sense! I'll start making some issues as I come across things (haven't looked at the code but will also see if I can fix them in a PR too).

Most of the lessons from his articles include the complete code at the bottom, eg: https://sbcode.net/tsl/raymarching/#final-script. In the code there you can see the most common type issue is defining TSL functions with Fn.

[Methuselah96]

👍 The Fn issue is probably reported in #1808, I haven't had time to take a look at it yet

[Methuselah96]

The TSL types are a lot easier to reason about after getting rid of the ShaderNodeObject type in #1839, so hopefully improvements should come a lot faster now