CLR Nested Pool support clarification #309
Merged
Conversation
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
…ng/removing notes is easier than removing/adding all references.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
mkflow27
approved these changes
Jan 19, 2026
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.
Since we are not deploying V3 of the CLR for now (which supports nested operations), the current docs are a bit misleading. We'd already updated them to reflect V3, assuming it would be deployed, as it's been ready since last October.
Rather than remove the functions (and have to add them back in later when we eventually do release it), this PR just adds a note that nested operations are supported in V3, which has not yet been deployed.