OpenHFT / OpenHFT/Zero-Allocation-Hashing
Any plan to remove `Unsafe` usage ?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 845
- Forks
- 140
- Avg merge
- 12d 38m
- Merged PRs (30d)
- 2
Description
Projects that rely on this library will receive warnings when running in JDK 24 version.
refer: https://github.com/sbt/sbt/issues/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/
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the net.openhft.hashing.UnsafeAccess class and auditing how it uses sun.misc.Unsafe. Read the linked JDK 24 warning context and JEP 471, then determine the scope of replacing or removing those calls. Done is an agreed, concrete migration plan that addresses the reported warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100