https://github.com/ruby/tempfile/commit/297bdf2c8d

`IO::NULL`'s underlying file `/dev/null` is not always available on
WASI, so use of the file on top-level code (introduced in
https://github.com/ruby/tempfile/pull/36) causes tempfile library not
to work at all on WASI.

https://github.com/ruby/tempfile/commit/d50939890e

https://github.com/ruby/tempfile/commit/2ff9b3ccef

https://github.com/ruby/tempfile/commit/7052805029

https://github.com/ruby/tempfile/commit/67ce897727

https://github.com/ruby/tempfile/commit/f677941ea2

As @jeremyevans pointed out for commit eb2d8b1:

> Each Tempfile instance has a separate File instance and file descriptor:
>
>   t = Tempfile.new
>   t.to_i # => 6
>   t.dup.to_i => 7

FinalizerManager will keep track of the open File objects for the
particular file and will only unlink the file when all of the File objects
have been closed.

https://github.com/ruby/tempfile/commit/753ab16642

The Closer and Remover finalizers are defined on different objects in
Tempfile. The Closer is defined on the Tempfile object while the Remover
is defined on the finalizer_obj. This means that there is no guarantee
of the finalizer order.

On Windows, we must close the file before removing it because we cannot
remove an open file. But since the order is not guaranteed, the GC may
run the Remover finalizer first, which will fail with an Errno::EACCES
(Permission denied @ apply2files).

This commit changes it so that both the Closer and Remover finalizers
are defined on the finalizer_obj, which guarantees the order that it is
ran.

https://github.com/ruby/tempfile/commit/eb2d8b1175