This statement wasn't useful, as elements was already null to begin with,
but also because onOutOfMemoryError doesn't generally return.
The addition of noreturn and its application to onOutOfMemoryError means
that this could trigger a warning in a future release.
https://github.com/dlang/druntime/pull/3447#issuecomment-822892222