sparse_strips: Document caveats more clearly - #1770
Merged
Merged
Conversation
nicoburns
approved these changes
Jul 27, 2026
Comment on lines
+93
to
+94
| //! - Some features are not yet supported and may panic, including filters during multi-threaded | ||
| //! rendering and complex filter graphs. |
Contributor
There was a problem hiding this comment.
It would be nice to be comprehensive here (I think this list might be, but isn't word as if it is)
Collaborator
Author
There was a problem hiding this comment.
Yes should be exhaustive, will reword it.
LaurenzV
enabled auto-merge
July 28, 2026 19:03
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
2 participants
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.
Since we want to make a 0.1 release, we should start advertising the current state and capabilities more prominently but also add more explicit warnings for current limitations.