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
Possible Undefined Behavior with Map::new
in safe Rust
#69
Comments
@cafce25 can you please suggest how to solve this? We have to do here something very similar to what |
@cafce25 in the meantime, I introduced a fix (0c81995), per this recommendation: https://stackoverflow.com/a/76091714/187141 However, the performance degraded because of this fix :( |
@rultor release, tag is |
@cafce25 @yegor256 Oops, I failed. You can see the full log here (spent 3min)
|
@rultor release, tag is |
I think
|
@cafce25 thanks, I replaced assignments with |
I see, I only read |
As it's currently written the new in
src/ctors.rs
can lead to undefined behavior in safe Rust. You can invoke it with the following test:I'm either getting a
SIGILL
orSIGSEGV
depending on the actual conditions when running tests in release withThe text was updated successfully, but these errors were encountered: