-
Notifications
You must be signed in to change notification settings - Fork 1.4k
functools.partial #5825
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
functools.partial #5825
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Callable implementation has a potential issue with keyword validation.
The callable logic correctly merges arguments and keywords, but there's an inconsistency in keyword validation that could cause runtime errors.
The keyword validation in the callable implementation differs from the constructor. In the constructor, all keywords are converted to interned strings, but in the callable, existing keywords are validated to be strings and could fail:
// Add keywords from self.keywords for (key, value) in inner.keywords.clone() { - let key_str = key - .downcast::<crate::builtins::PyStr>() - .map_err(|_| vm.new_type_error("keywords must be strings".to_owned()))?; - final_kwargs.insert(key_str.as_str().to_owned(), value); + // Keywords should already be strings from construction, but handle gracefully + let key_str = if let Ok(s) = key.downcast::<crate::builtins::PyStr>() { + s.as_str().to_owned() + } else { + // This shouldn't happen if construction is correct, but handle it + key.str(vm)?.as_str().to_owned() + }; + final_kwargs.insert(key_str, value);This ensures consistency with the construction logic where keywords are always stored as strings.
📝 Committable suggestion
🤖 Prompt for AI Agents