RustyYato

I would also recommend not using a single letter generic parameter in macros because it will easily conflict with the users of the macro. (In this case I had a...

@gorilskij I don't see how this is a big issue. Obviously we have to preserve `true` and `false` and be inconsistent with CamelCase How is this that bad though?

@gorilskij > There is another, more serious point. As proven by the fact that false is 0 and true is 1, bool is more than just a simple 2-variant enum,...

> What about if/else though? If bool is made to look like any other 2-variant enum won't it seem strange that it alone can be used in those statements? Opening...

@gorilskij as @varkor said it would reduce special casing the compiler, so it would make the compiler simpler. Special casing only makes things more complex, not the other way around....

Note: The UB comes from (quoting the [docs](https://doc.rust-lang.org/std/primitive.pointer.html#method.offset_from)) > If any of the following conditions are violated, the result is Undefined Behavior: > > * Both the starting and other...

@SimonSapin or we can add bounds to `Lazy` like so ```rust struct Lazy { .. } ``` and use it like this, ```rust static FOO: Lazy Foo> = Lazy(foo); ```

@SimonSapin I'm not sure what you are asking, I didn't use `_` anywhere in my example. It would be nice if we could have type inference in `static`/`const` that only...

Given that the linked crate has ~50k downloads over the course of a 1 1/2 years, I'm not inclined to believe that it's a "core feature". This should stay as...

@RalfJung what about unaligned volatile operations, right now `{read, write}_volatile` assume that the input pointer is aligned, and you would need `copy_volatile` at least to get unaligned volatile reads and...