fix: TypeGPU functions using TGSL dependencies declaration order#1522
Merged
aleksanderkatan merged 9 commits intomainfrom Jul 22, 2025
Merged
fix: TypeGPU functions using TGSL dependencies declaration order#1522aleksanderkatan merged 9 commits intomainfrom
aleksanderkatan merged 9 commits intomainfrom
Conversation
|
pkg.pr.new packages benchmark commit |
Collaborator
People coming from a non-WGSL background, or people that don't yet know recursion is not permitted in WGSL could look at that error and think it's a problem with the library. I think we should throw a descriptive error in this case. I'll make an issue for this. |
Collaborator
|
Here's the issue: #1523 |
This reverts commit a56e883.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The change allows for a function to reference another function defined later on.
This could potentially lead to people attempting to write recursive functions.
TypeScript screams when either of the following happens (something something any):
However, the following is fine:
and in this case we get a stack overflow:
Should we try to detect this situation? This would probably require resolve to hold a set of items it is currently trying to resolve, it seems pretty doable. On the other hand, this is already illegal in wgsl, and it is not too difficult to know what is going on when seeing an error like this.