Any plan to remove `Unsafe` usage ?

[counter2015]

Projects that rely on this library will receive warnings when running in JDK 24 version.

refer: sbt/sbt#8073

WARNING: Please consider reporting this to the maintainers of class net.openhft.hashing.UnsafeAccess
WARNING: sun.misc.Unsafe::arrayBaseOffset will be removed in a future release
WARNING: A restricted method in java.lang.System has been called

Is there any plan to remove Unsafe usage?

see also: https://foojay.io/today/unsafe-is-finally-going-away-embracing-safer-memory-access-with-jep-471/

[pradn]

A major user of this library is parquet-java, see related issue. I hope the issue can be solved in this repo by the Zero-Allocation-Hashing maintainers.

[lizlooney]

The memory access APIs in sun.misc.Unsafe were deprecated in JDK 23. They are scheduled to be REMOVED from the JDK after JDK 26.

[gzm55]

VarHandle was discussed and profiled in #67 and the results are different on environments. This unsafe functions called by this project are pluggable behind Access interface.

We could have two implementations, UnsafeAccess and VarHandleAccess. In building stage, use an separated module for UnsafeAccess to build with JDK<23. In the runtime, select a proper access instance based on the running JDK/JRE or the user configs.

[bmarwell]

@peter-lawrey @james-mcsherry @tgd this really needs your attention. It has been a year, and JDK 26 is going to be released in the next two months. Apache Maven Build Cache Extension is also a major user of this library.

[tgd]

Hi @bmarwell - thanks for flagging this again - this is very much on our roadmap and we will be publishing some more information soon.