-
Notifications
You must be signed in to change notification settings - Fork 769
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
Update new_closure_bound closure signature #3883
Conversation
6ab1624
to
fd380b1
Compare
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.
LGTM 🚀
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.
Thanks for picking this one up! I have a suggestion, which is sort of for my own learning too 😂
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.
Thanks both! One final thought from me...
Co-authored-by: Icxolu <[email protected]>
Co-authored-by: David Hewitt <[email protected]>
191ce6e
to
c7b1e45
Compare
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.
Thanks both, this looks correct and elegantly implemented!
Following on from #3877, I noticed that
PyCFunction::new_closure_bound
has a bound that still uses the GIL ref api for the closure. This updates that to use theBound
api instead.