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

Remove finalizer method bodies and bounds from implementations for standard library types #183

Conversation

steffahn
Copy link
Contributor

These are already handled by Trace::finalize_glue; fixes #182

The macro #[derive(Finalize)] was already correctly generating empty Finalize implementations.

…andard library types

These are already handled by Trace::finalize_glue; fixes #182

The macro #[derive(Finalize)] was already correctly generating
empty Finalize implementations.
@andersk
Copy link
Collaborator

andersk commented Nov 26, 2024

Are you interested in adapting your reproducer into a test case for gc/gc/tests?

@Manishearth Manishearth merged commit f7232e2 into Manishearth:master Nov 27, 2024
1 check passed
@steffahn steffahn deleted the remove-additional-recursive-finalize-calls branch November 27, 2024 02: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.

Finalize implementations for std types are largely wrong, many unnecessary extra finalize calls
3 participants