rust/tests/ui/transmutability/issue-101739-1.stderr

error[E0412]: cannot find type `Dst` in this scope
  --> $DIR/issue-101739-1.rs:8:9
   |
LL |         Dst: TransmuteFrom<Src, ASSUME_ALIGNMENT>,
   |         ^^^ not found in this scope

error: the constant `ASSUME_ALIGNMENT` is not of type `Assume`
  --> $DIR/issue-101739-1.rs:8:14
   |
LL |         Dst: TransmuteFrom<Src, ASSUME_ALIGNMENT>,
   |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `Assume`, found `bool`
   |
note: required by a const generic parameter in `TransmuteFrom`
  --> $SRC_DIR/core/src/mem/transmutability.rs:LL:COL

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0412`.
add a ui test for #101739 2022-10-03 01:02:38 -05:00			error[E0412]: cannot find type `Dst` in this scope
check if const is ADT or not 2022-10-03 03:51:18 -05:00			`--> $DIR/issue-101739-1.rs:8:9`
add a ui test for #101739 2022-10-03 01:02:38 -05:00			`\|`
safe transmute: Rename `BikeshedIntrinsicFrom` to `TransmuteFrom` 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 2024-08-27 09:05:54 -05:00			`LL \| Dst: TransmuteFrom<Src, ASSUME_ALIGNMENT>,`
add a ui test for #101739 2022-10-03 01:02:38 -05:00			`\| ^^^ not found in this scope`

Use param's real type in try_eval_lit_or_param 2023-03-09 14:49:05 -06:00			error: the constant `ASSUME_ALIGNMENT` is not of type `Assume`
			`--> $DIR/issue-101739-1.rs:8:14`
add a ui test for #101739 2022-10-03 01:02:38 -05:00			`\|`
safe transmute: Rename `BikeshedIntrinsicFrom` to `TransmuteFrom` 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 2024-08-27 09:05:54 -05:00			`LL \| Dst: TransmuteFrom<Src, ASSUME_ALIGNMENT>,`
			\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `Assume`, found `bool`
Use param's real type in try_eval_lit_or_param 2023-03-09 14:49:05 -06:00			`\|`
safe transmute: Rename `BikeshedIntrinsicFrom` to `TransmuteFrom` 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 2024-08-27 09:05:54 -05:00			note: required by a const generic parameter in `TransmuteFrom`
Use param's real type in try_eval_lit_or_param 2023-03-09 14:49:05 -06:00			`--> $SRC_DIR/core/src/mem/transmutability.rs:LL:COL`
add a ui test for #101739 2022-10-03 01:02:38 -05:00
Re-enable `ConstArgKind::Path` lowering by default ...and remove the `const_arg_path` feature gate as a result. It was only a stopgap measure to fix the regression that the new lowering introduced (which should now be fixed by this PR). 2024-09-08 00:49:25 -05:00			`error: aborting due to 2 previous errors`
add a ui test for #101739 2022-10-03 01:02:38 -05:00
Re-enable `ConstArgKind::Path` lowering by default ...and remove the `const_arg_path` feature gate as a result. It was only a stopgap measure to fix the regression that the new lowering introduced (which should now be fixed by this PR). 2024-09-08 00:49:25 -05:00			For more information about this error, try `rustc --explain E0412`.