easymock / easymock/objenesis

Finalizability should be documented

Open
#69 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
630
Forks
95
Avg merge
5h 6m
Merged PRs (30d)
9

Description

Objects created without running a constructor cannot be automatically finalized; see https://bugs.openjdk.java.net/browse/JDK-6590839. For ObjenesisStd's default strategy on OpenJDK, this isn't a concern, because it uses the munged Object constructor; but for other Objenesis strategies, including the defaults for other JVMs, it may be. It'd be nice if this was documented (and better yet if there was a way to check it at runtime). Is ReferenceQueue behavior also affected (which would mean users couldn't just implement their own finalizer either)?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.