Skip to content
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 to pyo3 v0.22.5 #119

Merged
merged 3 commits into from
Oct 28, 2024
Merged

Update to pyo3 v0.22.5 #119

merged 3 commits into from
Oct 28, 2024

Conversation

benbrandt
Copy link
Contributor

Second attempt at solving the issues in #104

This time I didn't need to introduce any extra unsafe, and I think the signatures match the intention of the previous code as best as I can understand.

Second attempt at solving the issues in bytecodealliance#104

This time I didn't need to introduce any extra unsafe, and I think the signatures match the intention of the previous code as best as I can understand.
Copy link
Collaborator

@dicej dicej left a comment

Choose a reason for hiding this comment

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

Thanks for persisting on this!

Like I mentioned before, we'll eventually want to do some leak checking to make sure we're not accidentally bumping reference counts too high such that they never go to zero. That was already a hazard before this update, though.

@dicej dicej merged commit 881cdb4 into bytecodealliance:main Oct 28, 2024
3 checks passed
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