Cache optimized default searches - #68
Open
OskarEichler wants to merge 1 commit into
Open
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
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.
Summary
Reuse a bounded, thread-safe default
CachingRuntimefor optionlessJMESPath.searchcalls and cache optimized expression trees.This implements the maintainer direction recorded in #25 while preserving custom runtime options and the existing
Runtime/CachingParserAPIs.Reproduction
The current module-level helper constructs a new runtime/parser and re-optimizes on every call. A parser-count model proves one parse across repeated and concurrent default searches; nonempty runtime options still get isolated runtimes.
Verification
Compatibility
Calls with runtime options remain uncached and preserve their parser/error configuration. Cache size follows the existing 1,000-entry policy; optimized nodes are immutable during visits. Prepared with AI-assisted source review; no repository tests were changed.