Skip to content

move IntoPy::type_output to IntoPyObject::type_output#4657

Merged
davidhewitt merged 3 commits into
PyO3:mainfrom
Icxolu:move-type-output
Oct 26, 2024
Merged

move IntoPy::type_output to IntoPyObject::type_output#4657
davidhewitt merged 3 commits into
PyO3:mainfrom
Icxolu:move-type-output

Conversation

@Icxolu

@Icxolu Icxolu commented Oct 26, 2024

Copy link
Copy Markdown
Member

Part of #4618

This moves IntoPy::type_output to IntoPyObject::type_output. This is a breaking change, but this is an experimantel feature and the ergonomics of duplicating the API is pretty bad, because it would need fully qualified syntax on the callsite to determine the trait to use.

@Icxolu

Icxolu commented Oct 26, 2024

Copy link
Copy Markdown
Member Author

Not really sure why MSRV needs the additional lifetime bounds, but they should be implied anyway, so spelling them out should not really be a problem either.

@davidhewitt davidhewitt left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed, this is fine to do in my opinion. Weird about those inferred lifetimes, I guess we live with them for now.

@davidhewitt davidhewitt added this pull request to the merge queue Oct 26, 2024
Merged via the queue into PyO3:main with commit f536ece Oct 26, 2024
@Icxolu Icxolu deleted the move-type-output branch October 26, 2024 17:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants