(you get a rough predicition at best)
not to dunk on ppl working on the C standard (❤️), or compiler devs (❤️), but the intersection of C, IEEE754 and the reality of diverse hardware is just... really cursed.
CS PhD student at Heinrich-Heine-University. Interested in Formal Methods, Programming languages, specifications. Slowest possible person. Hopeless optimist. Uniquely unhinged.
Guard up, Heart open.
🏳️⚧️
(you get a rough predicition at best)
not to dunk on ppl working on the C standard (❤️), or compiler devs (❤️), but the intersection of C, IEEE754 and the reality of diverse hardware is just... really cursed.
sometimes i get questions asking me about some weird float code i wrote and ask why it's not included by default in our builds and i have to explain that ieee754 conformance allows for a surprising range of possible behaviors and binary formats (how it's laid out in memory and what the bits mean).
this often surprises people and it gives me validation that the inclusion of maybe overzealous checks that currently let builds fail on e.g. macOS was the right move until the code is rewritten.