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
26 lines
892 B
Plaintext
26 lines
892 B
Plaintext
error[E0277]: `&Packed<Two>` cannot be safely transmuted into `&Packed<Four>`
|
|
--> $DIR/reject_extension.rs:48:37
|
|
|
|
|
LL | assert::is_transmutable::<&Src, &Dst>();
|
|
| ^^^^ the referent size of `&Packed<Two>` (2 bytes) is smaller than that of `&Packed<Four>` (4 bytes)
|
|
|
|
|
note: required by a bound in `is_transmutable`
|
|
--> $DIR/reject_extension.rs:13:14
|
|
|
|
|
LL | pub fn is_transmutable<Src, Dst>()
|
|
| --------------- required by a bound in this function
|
|
LL | where
|
|
LL | Dst: TransmuteFrom<
|
|
| ______________^
|
|
LL | | Src,
|
|
LL | | {
|
|
LL | | Assume {
|
|
... |
|
|
LL | | },
|
|
LL | | >,
|
|
| |_________^ required by this bound in `is_transmutable`
|
|
|
|
error: aborting due to 1 previous error
|
|
|
|
For more information about this error, try `rustc --explain E0277`.
|