diff options
| author | Matthias Krüger <476013+matthiaskrgr@users.noreply.github.com> | 2025-07-03 05:21:36 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-07-03 05:21:36 +0200 |
| commit | bc0262d0f1bf9165e28c01b64fb0dd1a24534968 (patch) | |
| tree | 9e275fd8466532f354e5e3496cc74659f15d82ca /library/std/src/sys/net/connection/socket/wasip2.rs | |
| parent | 5aa7dd81d80db2a7e58344587a6e6ecbd2690510 (diff) | |
| parent | 8362508989c8941ccbba26aaa8c787cc492c6fef (diff) | |
| download | rust-bc0262d0f1bf9165e28c01b64fb0dd1a24534968.tar.gz rust-bc0262d0f1bf9165e28c01b64fb0dd1a24534968.zip | |
Rollup merge of #143327 - RalfJung:miri-type-validity-error, r=oli-obk
miri: improve errors for type validity assertion failures Miri has pretty nice errors for type validity violations, printing which field in the type the problem occurs at and so on. However, we don't see these errors when using e.g. `mem::zeroed` as that uses `assert_zero_valid` to bail out before Miri can detect the UB. Similar to what we did with `@saethlin's` UB checks, I think we should disable such language UB checks in Miri so that we can get better error messages. If we go for this we should probably say this in the intrinsic docs as well so that people don't think they can rely on these intrinsics catching anything. Furthermore, I slightly changed `MaybeUninit::assume_init` so that the `.value` field does not show up in error messages any more. `@rust-lang/miri` what do you think?
Diffstat (limited to 'library/std/src/sys/net/connection/socket/wasip2.rs')
0 files changed, 0 insertions, 0 deletions