fix error with named lifetimes in #[new] return types#5998
Merged
davidhewitt merged 1 commit intoPyO3:mainfrom Apr 24, 2026
Merged
fix error with named lifetimes in #[new] return types#5998davidhewitt merged 1 commit intoPyO3:mainfrom
#[new] return types#5998davidhewitt merged 1 commit intoPyO3:mainfrom
Conversation
Merging this PR will not alter performance
Comparing Footnotes
|
davidhewitt
pushed a commit
to davidhewitt/pyo3
that referenced
this pull request
May 1, 2026
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.
While exploring I noticed that
#[new]functions with named lifetimes in their output type give a compile error. This is because the type is used in our const specialization. There is no particular reason to block such types, most notableBoundis one of them, so this fixes that.