This is interesting. Java desperately needs an array of struct for type safe sugar over high performance arenas, but the areas you’d turn to this would be in a zero allocation effort where the cost of the this library’s off-heap and the object allocation in the getters and setters etc largely negate the advantages for a lot of use cases.
kosolam2026-05-12 05:04
ENGLISH (원문)
Nice. Very clean api.
joe_mwangi2026-05-12 05:07
ENGLISH (원문)
Yup. Totally agree. Java does needs an array of structs. Hopefully value classes will help out through flattened array. But in future, one can use value records with this library with probable zero cost allocation. But the library doesn't use any reflection calls for get and set hence high performance as a result, and using records helps a lot with escape analysis. Planning to do some serious benchmarks soon. Some preliminary tests shows it's similar to c code (example code in test package). Performance suffers if record fields are arrays due to heap allocation of arrays.
joe_mwangi2026-05-12 05:10
ENGLISH (원문)
Thanks. Main goal. Unions is where I decided to pause - no simple and ergonomic way to do it at the moment.
댓글
4