You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest published version (0.6.12) does not include these commits, which includes #162 which removes mem::uninitialized uses and lets the crate run under miri.
I was trying to run what appears to be a UB-based issue in a rust-analyzer (rowan) patch under miri and ran into this.
You should probably also consider submitting a RustSec advisory for the miri-disapproved mem::uninitialized usage.
Miri evaluation error
error[E0080]: Miri evaluation error: type validation failed: encountered uninitialized bytes at [0].inner.value, but expected a valid enum discriminant
--> D:\usr\.cargo\registry\src\github.com-1ecc6299db9ec823\smallvec-0.6.12\lib.rs:409:49
|
409 | data: SmallVecData::from_inline(mem::uninitialized()),
| ^^^^^^^^^^^^^^^^^^^^ Miri evaluation error: type validation failed: encountered uninitialized bytes at [0].inner.value, but expected a valid enum discriminant
Side note: master still has a toml advertising a version number of 0.6.10.
The text was updated successfully, but these errors were encountered:
The latest published version (0.6.12) does not include these commits, which includes #162 which removes
mem::uninitialized
uses and lets the crate run under miri.I was trying to run what appears to be a UB-based issue in a rust-analyzer (rowan) patch under miri and ran into this.
You should probably also consider submitting a RustSec advisory for the miri-disapproved
mem::uninitialized
usage.Miri evaluation error
Side note: master still has a toml advertising a version number of
0.6.10
.The text was updated successfully, but these errors were encountered: