Editions Ideas

[monkyyy]

On Sunday, 14 December 2025 at 20:36:42 UTC, Walter Bright wrote:
> Not following the IEEE 754 spec to the letter means "D has a 
> broken floating point implementation." That's not going to 
> happen. People write very carefully crafted floating point code 
> relying on exact adherence to the spec.

And? Specs are just words written by mere mortals, it be a trade 
off with upsides to ignore them. It be nice if the 2nd most 
important type at least had some level of consistency with the 
1st.

I understand some airplane surgery theory tells ya to want 
float.init to be nan; I just see a pile of complexity for trying 
to meta program, Im aware of like 3 things that make the 
landscape of d's type theory hard, ieee floats + your thoerys are 
an as an unforced error as autodecoding is.

Floats being number-y and kinda nullable-y, means my goals of 
extremely strong api's gets to consider how to combine nullables 
with bools instead of nullables being a simply a container and 
segmented completely elsewhere. But nah, we get to merge it all 
together in a big ball of complexity.