feat(rsc): expose callable argument metadata - #1389
Closed
hi-ogawa wants to merge 8 commits into
Closed
Conversation
Co-authored-by: OpenCode <noreply@opencode.ai>
Co-authored-by: OpenCode <noreply@opencode.ai>
Co-authored-by: OpenCode <noreply@opencode.ai>
Co-authored-by: OpenCode <noreply@opencode.ai>
Co-authored-by: OpenCode <noreply@opencode.ai>
Co-authored-by: OpenCode <noreply@opencode.ai>
Co-authored-by: OpenCode <noreply@opencode.ai>
Co-authored-by: OpenCode <noreply@opencode.ai>
Contributor
Author
|
Closing since this should split to |
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.
"use cache"Server Functions #1336"use cache"Cache Keys #1392"use cache"functions vercel/next.js#72506Framework-owned callable wrappers cannot recover source parameter admission or generated closure capture boundaries from
Function.length. This matters when framework-supplied arguments should not affect fixed-signature cache keys while declared arguments and decoded captures should.This PR exposes
{ count, hasRest }for statically known source functions andboundArgumentCountfor inline directive lowering. The bound count describes the generated call shape, so direct captures occupy their actual number of slots while encoded captures occupy one. The callable cache example consumes this metadata and demonstrates fixed-prefix admission, rest pass-through, and decoded capture identity in development and production.