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
According to a recent article, at least one-third of the Java ecosystem is still comprised of Java 8 applications. The primary choice behind using Java 11 for this library was because of the java.lang.ref.Cleaner API, which was introduced in Java 9. This API provides a memory safety net when the user forgets to appropriately clean up the native resources associated with External instances.
Although migrating to Java 8 would undoubtedly contribute to the library's overall adoption, removing the Cleaner API is out of the question. We therefore need to devise alternative means by which we can guarantee native resource cleanup.
This discussion was converted from issue #70 on November 12, 2023 12:54.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
According to a recent article, at least one-third of the Java ecosystem is still comprised of Java 8 applications. The primary choice behind using Java 11 for this library was because of the
java.lang.ref.Cleaner
API, which was introduced in Java 9. This API provides a memory safety net when the user forgets to appropriately clean up the native resources associated withExternal
instances.Although migrating to Java 8 would undoubtedly contribute to the library's overall adoption, removing the
Cleaner
API is out of the question. We therefore need to devise alternative means by which we can guarantee native resource cleanup.Beta Was this translation helpful? Give feedback.
All reactions