Re:Data Processing Benchmark Featuring Rust, Go, Swift, Zig,...
by pron on Sunday February 01, 2026 @07:14AM
(#46845668)
You're right that Java lacks inline types (although it's getting them really soon, now), but the main cost of that isn't because of stack allocation (because heap allocations in Java don't cost much more than stack allocations), but because cache misses due to objects not being inlined in arrays.
[ Parent
| on HN ]
Re:Data Processing Benchmark Featuring Rust, Go, Swift, Zig,...
by pron on Sunday February 01, 2026 @07:40PM
(#46851003)
P.S.
Even for flattened types, the "abstraction penalty", or, more precisely, its converse, the "concreteness penalty", in Java will be low, as you don't directly pick when an object is flattened. Instead, you declare whether a class cares about identity or not, and if not, the compiler will transparently choose whether and when to flatten the object, depending on how it's used.