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
Disable debug_asserts inside std due to poor UX (rust-lang#1791)
This is a possible workaround for now to improve the UX around UB
detection in intrinsics when using the MIR Linker. The issue is tracked
here:
model-checking/kani#1740
Basically, the rust toolchain uses a release build that removes all
debug assertions from the standard library. When we switched to using
our custom build of the `std` we decided to enable the debug assertions
in order to catch more potential UBs. However, the UX is not always
great. The assertions don't have any clear descriptions and they may
fail in unexpected places. E.g.: The violation of an intrinsic safety
condition triggers the following failures:
```
> Failed checks: Called `Option::unwrap()` on a `None` value
```
0 commit comments