Some HN discussion here: https://news.ycombinator.com/item?id=9943589
I'd be keen to know more but he hasn't really published any details other than his book <http://www.amazon.com/The-End-Error-Computing-Computational/dp/1482239868>. Based on the free preview, it looks like a bit of a diatribe rather than a detailed technical proposal, but you can look at his mathematica code here <https://www.crcpress.com/The-End-of-Error-Unum-Computing/Gustafson/9781482239867> . On Saturday, 25 July 2015 15:22:31 UTC+1, Simon Danisch wrote: > > How cool! > I don't know much about this matter, but this looks very exciting! > Julia seems to be a good fit to prototype this! > > Am Samstag, 25. Juli 2015 15:11:54 UTC+2 schrieb Job van der Zwan: >> >> So I came across the concept of UNUMs on the Pony language mailing list >> <http://lists.ponylang.org/pipermail/ponydev/2015-July/000071.html> this >> morning. I hadn't heard of them before, and a quick search doesn't show up >> anything on this mailing list, so I guess most people here haven't either. >> They're a proposed alternate encoding for numbers by John L. Gustafson. >> This presentation by him sums it up nicely: >> >> http://sites.ieee.org/scv-cs/files/2013/03/Right-SizingPrecision1.pdf >> >> “Unums”(universal numbers) are to floating point what floating point is >>> to fixed point. >>> Floating-point values self-describe their scale factor, but fix the >>> exponent and fraction size. Unums self-describe the exponent size, fraction >>> size, and inexact state, and include fixed point and IEEE floats as special >>> cases. >>> >> >> The presentation can be seen here, provided you have the Silverlight >> plugin: >> >> >> http://sites.ieee.org/scv-cs/archives/right-sizing-precision-to-save-energy-power-and-storage >> >> Now, I don't know enough about this topic to say if they're a good or bad >> idea, but I figured the idea is interesting/relevant enough to share with >> the Julia crowd. >> >> I'm also wondering if they could be implemented (relatively) easily >> within Julia, given its flexible type system. If so, they might provide an >> interesting advanced example, no? >> >
