You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been digging in to OpenAL and noticed some usages of sun.misc.Unsafe + a requires jdk.unsupported in the module-info.
Given that Unsafe will be removed at some point, what are the current plans for moving away from it? Are there particular upcoming APIs (like the foreign memory api? MultiReleaseMemCopy is where i found one of the usages.) that are being waited on?
The text was updated successfully, but these errors were encountered:
LWJGL 3 supports Java 8 and that won't change before a new major version. Thus, just the release of the new FFI in Java 22 is not enough to replace Unsafe. Further, migrating to the new FFI is a significant undertaking and will probably not happen before value/primitive classes (or whatever they end up being called) are available.
Sure, Unsafe is being removed, but slowly. If this happens before value types are made available, this will be revisited, but that's unlikely. (I would actually be surprised if unsafe removed in the next four years.)
Question
I've been digging in to OpenAL and noticed some usages of
sun.misc.Unsafe
+ arequires jdk.unsupported
in the module-info.Given that
Unsafe
will be removed at some point, what are the current plans for moving away from it? Are there particular upcoming APIs (like the foreign memory api?MultiReleaseMemCopy
is where i found one of the usages.) that are being waited on?The text was updated successfully, but these errors were encountered: