On Tue, 18 Aug 2026 10:40:01 GMT, Johan Sjölen <[email protected]> wrote:
>> When creating a new array of type T, the type T should not be initialized. >> This is the case for all types (classes and value classes). The reason that >> this code was added is probably because in a previous Valhalla model, the VM >> filled in a default value for each flattened array element, which >> necessitated the initialization of the class. >> >> --------- >> - [X] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > Johan Sjölen has updated the pull request incrementally with one additional > commit since the last revision: > > Document the method src/java.base/share/classes/jdk/internal/misc/Unsafe.java line 325: > 323: * @return an array whose contents is potentially uninitialized > 324: */ > 325: public native Object[] newSpecialArray(Class<?> componentType, Hello Johan, should there be an explicit check for `componentType` being non-null (and document that it expects non-null)? Right now the following call crashes a (release build) JVM: public class Foo { public static void main(final String[] args) throws Exception { jdk.internal.misc.Unsafe.getUnsafe().newSpecialArray(null, 2, 0); } } ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/32193#discussion_r3806141076
