Fun fact - Google Maps does something similar to this in WebGL in order to keep accurate coordinates across a planet-sized map using only 32-bit floats.
I have a Go library implementing double-double arithmetic (and also exponentials, logarithms, trigonometry...): https://github.com/ncruces/dbldbl
Mostly useless, but was quite fun to write.
Could be a neat post, but it was too obviously LLM-generated for me to care about reading it deeply. I’m really fine with people using LLMs to write code and understand stuff, but at least drop a disclaimer when you’re blogging straight Claude text.
At least Dekker is referenced.
If you need that precision, especially for position and not values, why use floats at all?
Could call it... 'a Hamburglar'
Reads like AI slop. It circles around the point, uses C# examples while talking about FPU, duplicates examples and so on.
AI has rediscovered https://www.davidhbailey.com/dhbsoftware/ and similar? Or are there algorithmic improvements? Without referencing established double-double work it's hard to know.