Repository navigation
NativeObject: AtomicReference pointer and AtomicBoolean immortal - #357
Merged
Merged
Conversation
…an AtomicBoolean Replaces the volatile field plus VarHandle (Sonar S3077) with plain atomics; the cost is two small allocations per wrapper. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
NativeObjectholds its pointer in anAtomicReference<MemorySegment>andimmortalin anAtomicBoolean, replacing thevolatilefield swapped through aVarHandle(and its static block). Fixes Sonar S3077 onNativeObject:36without a suppression.NativeObjectParentjavadoc updated to match.Test plan
./mvnw test -pl core -am,./mvnw package -pl core -am -DskipTests🤖 Generated with Claude Code