rust/tests/crashes/124207.rs

//@ known-bug: #124207
#![feature(transmutability)]
#![feature(type_alias_impl_trait)]
trait OpaqueTrait {}
type OpaqueType = impl OpaqueTrait;
trait AnotherTrait {}
impl<T: std::mem::TransmuteFrom<(), ()>> AnotherTrait for T {}
impl AnotherTrait for OpaqueType {}
pub fn main() {}
Revert 'Stabilize -Znext-solver=coherence' 2024-09-11 17:57:04 -04:00			`//@ known-bug: #124207`
crashes: add a couple more ICE tests 2024-04-21 21:01:04 +02:00			`#![feature(transmutability)]`
			`#![feature(type_alias_impl_trait)]`
			`trait OpaqueTrait {}`
			`type OpaqueType = impl OpaqueTrait;`
			`trait AnotherTrait {}`
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			`impl<T: std::mem::TransmuteFrom<(), ()>> AnotherTrait for T {}`
crashes: add a couple more ICE tests 2024-04-21 21:01:04 +02:00			`impl AnotherTrait for OpaqueType {}`
			`pub fn main() {}`