Optimize codecs context cacheing #1195
Merged
Conversation
This file contains 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
We should really copy the cached codex context for cloned Options instances (unless .withCodecs() was called).
jaclarke
reviewed
Feb 13, 2025
Comment on lines
+285
to
+286
| clone.cachedCodecContext = this.cachedCodecContext; | ||
| clone.cachedCodecContextVer = this.cachedCodecContextVer; |
There was a problem hiding this comment.
clone.cachedCodecContext = this.makeCodecContext();
If we want maximum caching™ we should make sure the cachedCodecContext is actually initalised before we copy it.
There was a problem hiding this comment.
There's a check when the cache is used, I think that check is enough.
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.
We should really copy the cached codex context for cloned Options instances (unless .withCodecs() was called).