lcnr

@rustbot second

@rustbot second

cc @oli-obk @RalfJung @eddyb

We detect it in the final value of a constant afaict. So `const N: bool = unsafe { std::mem::transmute::(2) };` already causes a compile time error. ``` error[E0080]: it is...

I don't see why "The problem with this definition is that it is uncheckable" is a problem in practice. Just like the borrow checker prevents programs which are theoretically correct,...

> Such a method would likely trigger ICEs all over the place. Then it has to be unsafe, because it can trigger undefined behavior. It seems like I also have...

> ICEs have nothing to do with UB. In other words, even unsafe code must not be able to trigger ICEs during compilation. This seems like a weird restriction on...

Ok, so from what I can tell, a given crate/type/whatever is well formed iff the language accepts it. IOW both things which are not well formed but are currently accepted...

solved by setting max speed to `120`. Still fairly annoying

hmm, this looks like contexts simply shouldn't be `Send`/`Sync` or something like that :thinking: so I believe that instead of supporting this, it's probably far easier to error. Do you...