Set finalizer on underlying Memory
object in Julia 1.11+
#11
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.
In Julia 1.11+ with the new
Memory
object, the memory is not actually owned by the constructedArray
and therefore the finalizer may trigger too early when the underlying memory is transfered from anArray
to a different kind of owner (such asIOBuffer
).Fix this by conditionally checking for the Julia 1.11+ behavior, and instead setting the finalizer on the
Memory
, if necessary.Duplicates the improvement made to the Mmap stdlib's implementation: JuliaLang/julia#54210