-
Notifications
You must be signed in to change notification settings - Fork 13.3k
segfault: alt
allows uniqueness violation
#2657
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
Comments
This is thematically related to #2329. |
D'oh. This is my fault, liveness or borrowck should prevent moves from bindings---probably borrowck. In any case, this would go away if #2329 were implemented. But it'd be easy to fix in the meantime. |
Actually, I'm a bit surprised that this passes... I should look into this. |
Oh, right, the actual bug here is that borrowck doesn't understand |
Related to issue #2657, but this is not a complete fix.
this should be fully fixed now. |
Add miri_alloc, miri_dealloc `miri_alloc` and `miri_dealloc` are basically the same as `__rust_alloc` and `__rust_dealloc` respectively, but without the check for a global allocator. This should allow bootstrapping an allocator in environments, where no fundamental way of allocating memory is available (`no_std` + `alloc` in Miri).
Add miri_alloc, miri_dealloc `miri_alloc` and `miri_dealloc` are basically the same as `__rust_alloc` and `__rust_dealloc` respectively, but without the check for a global allocator. This should allow bootstrapping an allocator in environments, where no fundamental way of allocating memory is available (`no_std` + `alloc` in Miri).
We shouldn't be able to duplicate a reference to a unique value. But:
The
some()
isn't even necessary.The text was updated successfully, but these errors were encountered: