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.
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
add
FromPyObjectBound
trait for extracting&str
without GIL Refs #3928add
FromPyObjectBound
trait for extracting&str
without GIL Refs #3928Changes from 1 commit
bd01818
d6e2ca5
7b75601
ea25871
ee30dd9
50277e9
263fc02
4dad333
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
We could also already call this
from_py_object
, but maybe it's better to have a clear distinction for now...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.
I think the one question which made me hesitate on encouraging users to use this trait too much (and also make this name clunky) is that I think to resolve the
TODO
in instance.rs:we would need to make this trait accept
ob: Borrowed<'a, 'py, PyAny>
as the input, as that's basically&Bound
with additional flexibility on the relationship between'a
and'py
.It felt to me that this is a hurdle we can cross down the line, and working with
Bound
for now keeps it simple...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.
Ah, using
Borrowed
there would certainly be an option. I agree that this is a question best answered once we actually removed the gil-refs and do the final migration. We could also seal this trait for now (but maybe that's a bit drastic). Removing a seal in a patch release, if it turns out to be necessary, would also be an option.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.
Let's seal this, and leave a note saying that "if you have a need to use this trait, please let us know and help us work out the design".
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.
Ok, I pushed an additional commit to seal the trait.