Oli Scherer

https://github.com/rust-lang/rfcs/pull/3016 has been merged, we can now start stabilization requests to the lang team for individual unsafe things like transmute or raw pointer derefs. valtrees are on ice until July...

> What was the reason for the limitation to begin with? It required additional logic to be able to differ, so the original implementation didn't. This RFC is the result...

This is not actually using the constness at all, afaict all calls of `apply` are runtime calls. So whatever guarantees you assumed either don't exist, or, assuming you meant to...

> using a system like https://blog.yoshuawuyts.com/const-syntax/ the bounds should probably be something like for const Trait meaning that the trait methods must callable at runtime and compiletime. The reason I...

This RFC only removes the restriction that const fn must behave the same at runtime and at compile time. The difference between const fn and runtime fn is still absolutely...

> * ideally, though likely as a matter of QOI rather than specification, we provide some further guarantees; e.g. if the constant evaluation path is taken, it is fully constant...

Oh heh. I'm sure this will cause ICEs, but that's still a fun experiment.

Cargo clippy forwards to cargo rustc and injects a custom compiler through the RUSTC env var. This way we avert these issues entirety. But it has the downside of overwriting...

I'm a big proponent of pattern types, but I have to agree this is not a good use case for it. On the topic at hand, do you want a...

I think even if we come up with a perfect `where` bound based system, having an escape hatch that you explicitly need to opt into is good. It may be...