Add deterministic resource cleanup pattern - #196
Merged
brunoborges merged 1 commit intoAug 26, 2026
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.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.
Finalization is deprecated for removal and cannot guarantee prompt or ordered cleanup. This adds a migration pattern showing deterministic resource management with
AutoCloseable, while retainingCleaneronly as a defensive fallback for leaked resources.The modern example isolates cleanup state in a static
Runnableso the cleaner action does not retain the registered resource. It also adds a Java 25 proof and inserts the pattern next to the existing try-with-resources entry in the I/O navigation chain.Fixes: #173