os-rust/tests/ui/transmutability/issue-101739-2.stderr

error[E0107]: trait takes at most 2 generic arguments but 5 generic arguments were supplied
  --> $DIR/issue-101739-2.rs:17:14
   |
LL |           Dst: TransmuteFrom<
   |                ^^^^^^^^^^^^^ expected at most 2 generic arguments
...
LL |                   ASSUME_ALIGNMENT,
   |  _________________________________-
LL | |                 ASSUME_LIFETIMES,
LL | |                 ASSUME_VALIDITY,
LL | |                 ASSUME_VISIBILITY,
   | |_________________________________- help: remove the unnecessary generic arguments

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0107`.
safe transmute: revise safety analysis Migrate to a simplified safety analysis that does not use visibility. Closes https://github.com/rust-lang/project-safe-transmute/issues/15 2024-02-26 16:49:25 +00:00			`error[E0107]: trait takes at most 2 generic arguments but 5 generic arguments were supplied`
			`--> $DIR/issue-101739-2.rs:17:14`
check if const is ADT or not 2022-10-03 17:51:18 +09: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 14:05:54 +00:00			`LL \| Dst: TransmuteFrom<`
			`\| ^^^^^^^^^^^^^ expected at most 2 generic arguments`
Retroactively feature gate `ConstArgKind::Path` 2024-08-19 01:14:09 +01:00			`...`
			`LL \| ASSUME_ALIGNMENT,`
			`\| _________________________________-`
			`LL \| \| ASSUME_LIFETIMES,`
			`LL \| \| ASSUME_VALIDITY,`
			`LL \| \| ASSUME_VISIBILITY,`
			`\| \|_________________________________- help: remove the unnecessary generic arguments`
check if const is ADT or not 2022-10-03 17:51:18 +09: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 01:49:25 -04:00			`error: aborting due to 1 previous error`
check if const is ADT or not 2022-10-03 17:51:18 +09: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 01:49:25 -04:00			For more information about this error, try `rustc --explain E0107`.