Remove Trace implementation for Rc #153
Merged
+0
−21
Conversation
This file contains 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
I’m not sure if these impls would work with a better tracing
algorithm, but they do not work correctly with this one.
let r = Rc::new(Gc::new(()));
Gc::new((Rc::clone(&r), r));
// → thread 'main' panicked at 'Can't double-unroot a Gc<T>'
Fixes Manishearth#134.
Signed-off-by: Anders Kaseorg <[email protected]>
This was referenced Dec 19, 2022
Merged
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.
I’m not sure if these impls would work with a better tracing algorithm, but they do not work correctly with this one.
Fixes #134.
I’m open to other suggestions, but I suspect the right way to support
Rc<T>would be with a trait that marksTas containing noGcdependencies (#109). Meanwhile, a user who needs such anRc<T>can#[unsafe_ignore_trace].