Jacob Lifshay

> Where will bf16 be located in libcore? The PPC and x86 floats will go in the relevant arch modules, but since bfloat is not arch-specific, it seems relevant to...

> Based on the description it's not even correct to describe it as "two f64's", it is one f64 and then a u64 with a bunch of extra mantissa bits....

one other option is we could copy the existing double-double crate and call it [twofloat](https://docs.rs/twofloat/0.7.0/twofloat/)

> I'm not exactly sure why the double-underscore convention was adopted for the x86 types, but if we're going for consistency, f80 should be called __m80. the double underscore is...

> > the double underscore is likely because C reserves all identifiers starting with `__` for the implementation. > > This isn't C, though. but the `__m128` naming comes from...

When does associated const code get run? at type definition? when substituting concrete types into generic arguments? never? so, if I write: ```rust pub struct S(T); impl S { const...

> I have added a paragraph proposing that they are evaluated never, aligning with the behavior of a named associated constant that is accessed never, but I'd welcome considering other...

so, basically as if: ```rust pub struct S(T, U); impl S { const _: () = ...; } ``` was instead written: ```rust pub struct S(T, U, PhantomData); impl S...

what happens when code pointers are bigger than data pointers? do you have to fall back on `transmute` to get the address, since casting to a data pointer will lose...

> usize is guaranteed to be the same size as a data pointer, so seemingly if cast to a data pointer would truncate, cast to usize would too. Does Rust...