Conversation
This branch has not been deployed
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.
memoizeassumes that required parameters are passed positionally. A unary call such asmemoized(x=1)raisesIndexError, while calls to a binary function with different keyword arguments can share the empty-tuple cache key and return the wrong result.Bind supplied keywords to the function signature before constructing the optimized cache key. Positional calls retain their existing keys, and equivalent positional and keyword calls share cached results.
Tests cover unary and binary functions, mixed and reordered arguments, cache reuse, and invalid keywords. The full test and doctest suites, benchmarks, style checks, and changed-file pre-commit hooks pass; tests and benchmarks also pass on Python 3.9, 3.14 and 3.15.