1ad218f3af
As our implementation of MCP411 nears completion and we begin to solicit testing, it's no longer reasonable to expect testers to type or remember `BikeshedIntrinsicFrom`. The name degrades the ease-of-reading of documentation, and the overall experience of using compiler safe transmute. Tentatively, we'll instead adopt `TransmuteFrom`. This name seems to be the one most likely to be stabilized, after discussion on Zulip [1]. We may want to revisit the ordering of `Src` and `Dst` before stabilization, at which point we'd likely consider `TransmuteInto` or `Transmute`. [1] https://rust-lang.zulipchat.com/#narrow/stream/216762-project-safe-transmute/topic/What.20should.20.60BikeshedIntrinsicFrom.60.20be.20named.3F
31 lines
1.1 KiB
Plaintext
31 lines
1.1 KiB
Plaintext
error[E0277]: `&[u8; 0]` cannot be safely transmuted into `&[u16; 0]`
|
|
--> $DIR/align-fail.rs:21:55
|
|
|
|
|
LL | ...tatic [u8; 0], &'static [u16; 0]>();
|
|
| ^^^^^^^^^^^^^^^^^ the minimum alignment of `&[u8; 0]` (1) should be greater than that of `&[u16; 0]` (2)
|
|
|
|
|
note: required by a bound in `is_maybe_transmutable`
|
|
--> $DIR/align-fail.rs:9:14
|
|
|
|
|
LL | pub fn is_maybe_transmutable<Src, Dst>()
|
|
| --------------------- required by a bound in this function
|
|
LL | where
|
|
LL | Dst: TransmuteFrom<Src, {
|
|
| ______________^
|
|
LL | | Assume {
|
|
LL | | alignment: false,
|
|
LL | | lifetimes: true,
|
|
... |
|
|
LL | | }
|
|
LL | | }>
|
|
| |__________^ required by this bound in `is_maybe_transmutable`
|
|
help: consider removing the leading `&`-reference
|
|
|
|
|
LL - assert::is_maybe_transmutable::<&'static [u8; 0], &'static [u16; 0]>();
|
|
LL + assert::is_maybe_transmutable::<&'static [u8; 0], [u16; 0]>();
|
|
|
|
|
|
|
error: aborting due to 1 previous error
|
|
|
|
For more information about this error, try `rustc --explain E0277`.
|