Yonggang Luo

Ping for this.

> `f64f64` is a bad name for type. Maybe `fxd64` (float extended double 64) is better. > > Having unified rule for naming is a benefit. For example, > >...

> > > 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...

> one other option is we could copy the existing double-double crate and call it [twofloat](https://docs.rs/twofloat/0.7.0/twofloat/) this comes with an issue that not the rust style like f16,f32,f64,f128

> > this comes with an issue that not the rust style like f16,f32,f64,f128 > > To echo something said by scottmcm on another thread: types representing 80-bit extended precision...

> 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. I'm not sure if...

> > this comes with an issue that not the rust style like f16,f32,f64,f128 > > To echo something said by scottmcm on another thread: types representing 80-bit extended precision...

Better split bf16 out of this, I think the main reason `f64f64` and `f80` is for keep ABI compatible with existing C libraries, but bf16 is not just for ABI...

The MSVC version are 40MB.

msvc build are running and show things