News for hackers. Stuff that matters.
Re:Almost Always Unsigned by masklinn on Sunday January 02, 2022 @08:49AM (#29768675)
> I can't think of a single time I've heard someone complain "I wish Java's long type supported up to 16 quintillion instead of a paltry 8 quintillion"

That Java has no support for unsigned integers is a very common complaint.

Re:Almost Always Unsigned by marginalia_nu on Sunday January 02, 2022 @09:07AM (#29768775)
It's one of my biggest complaints attempting to do systems programming in the language, that and the lack of 64bit mmap.
Re:Almost Always Unsigned by xxs on Sunday January 02, 2022 @09:46AM (#29769091)
I have no issue with the lack of unsigned - that's ok. It's a trivial workaround, as it's rare enough. However the lack of 64bit indices over memory mapped files blows indeed, with no easy (performant) replacement. It's doable but it'd require a shim over an array of ByteBuffer with the double indirection and pretty much inability for the JIT to optimize away all the bound checks.
Re:Almost Always Unsigned by hashmash on Sunday January 02, 2022 @10:39AM (#29769537)
I've had to resort to rolling my own mapping layer using JNA. Fortunately, 64-bit mmap support is being added as part of the Panama foreign-memory project.