Skip to content

Fix taking owned resource handles in Rust imports #669

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

Merged

Conversation

alexcrichton
Copy link
Member

I went ahead and did a bit more refactoring at the logic here since I think the old conditions aren't as applicable any more (they haven't aged well)

Closes #668

I went ahead and did a bit more refactoring at the logic here since I
think the old conditions aren't as applicable any more (they haven't
aged well)

Closes bytecodealliance#668
@alexcrichton
Copy link
Member Author

I'll also note that the exact way to get this all working in Rust is sort of a perpetual game of whack-a-mole. Short of setting up fuzzing to suss out issues I'm personally content to add individual test cases as they come up and constrain the logic to 'seems fine if it passes tests'

@sunfishcode sunfishcode merged commit f6004cd into bytecodealliance:main Sep 18, 2023
@alexcrichton alexcrichton deleted the fix-rust-own-in-import branch September 18, 2023 16:31
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.

Rust: error in record with resource
2 participants