Content-Length: 10770 | pFad | http://lwn.net/Articles/908312/

The road to Zettalinux [LWN.net]
|
|
Subscribe / Log in / New account

The road to Zettalinux

The road to Zettalinux

Posted Sep 16, 2022 13:29 UTC (Fri) by tux3 (subscriber, #101245)
In reply to: The road to Zettalinux by colejohnson66
Parent article: The road to Zettalinux

What about entropy coding with the short and longs? =)

The Rust integer types like i64 could map to "short long long", and even LLVM integers like i48 could be "short long short long".
Since there's some encoding space left with the short keyword as a useful escape keyword, let's also map the Rust unit type () to short bool, like this actual C++ paper proposed to replace void: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/...


to post comments

The road to Zettalinux

Posted Sep 16, 2022 13:36 UTC (Fri) by mathstuf (subscriber, #69389) [Link]

> short long short long

Do I apply the spiral rule to reading this type as well?

The road to Zettalinux

Posted Sep 17, 2022 19:50 UTC (Sat) by rav (subscriber, #89256) [Link]

> let's also map the Rust unit type () to short bool

Is short bool then going to be signed or unsigned (or something in between, like char)?

We would need unsigned short bool and signed short bool to have proper sign extension support when going from 0-bit values to e.g. 32-bit values.

And of course, don't forget the new stdint.h typedefs: uint0_t and int0_t (for unsigned short bool and signed short bool).


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds









ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: http://lwn.net/Articles/908312/

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy