-
Notifications
You must be signed in to change notification settings - Fork 13k
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
The Cell type may be unsound as it is currently implemented #10231
Comments
Hm, thinking about this, I feel like this may be a dupe of #8624. @nikomatsakis, can you confirm? (if so I'll close) |
I'll take a look and confirm. I am planning to fix #8624 this week, so ... |
could also be #5781 |
just-a-bug |
I...don't think this is still an issue. I tried to translate this test to modern syntax as best I could:
|
I'm not precisely sure what was the issue originally, it may have been #6801, since the older cell api involved a lot more closures. Might be worth digging up the original version of Rust and trying to track it down, since unsoundness is a big concern. |
Actually, quite likely this was #11385 (though in another guise) -- that is, an unsound result of variance inference. It "feels" right though without having reference to the original cell type I'm not able to completely spell out the chain of events. |
Closing, |
`invalid_regex`: Show full error when string value doesn't match source changelog: [`invalid_regex`]: Show full error when parsing non-literals or regular strings containing escape sequences Fixes rust-lang#4170, the escape sequence there causes the span to be incorrect which will have caused most of the confusion
Near the end
this
andthis2
are two mutable pointers to the same object, which I believe is unsound.Nominating, this is not good.
The text was updated successfully, but these errors were encountered: