Ruby

From what I understand, the real intent of this proposal is to "let the OS clean up after the generated tempfile". If so, I don't think the name create_io represents the intent.
I vote for adding a keyword argument to Tempfile.create.

Matz.

Previous discussions:

• https://bugs.ruby-lang.org/issues/11715@akr (Akira Tanaka) thinks it's a good idea to have an anonymous file, then name it afterwards.
• https://bugs.ruby-lang.org/issues/13743@akr (Akira Tanaka) is against the pull request which actually adds such feature (maybe it was the implementation and the idea was OK though).

Because the proposed Tempfile.create_io returns a non-File IO instance, there is no way to assign a path in this ticket.

matz (Yukihiro Matsumoto) wrote in #note-1:

From what I understand, the real intent of this proposal is to "let the OS clean up after the generated tempfile". If so, I don't think the name create_io represents the intent.
I vote for adding a keyword argument to Tempfile.create.

I updated the PR to change the interface:
I added unlink_first keyword argument for Tempfile.create.

f = Tempfile.create(unlink_first: true) # The file is already removed because unlink_first f.path # => "/tmp/" (no filename since no file) f.puts "foo" f.rewind f.read # => "foo\n" f.close Tempfile.create(unlink_first: true) {|f| # The file is already removed because unlink_first f.path # => "/tmp/" (no filename since no file) f.puts "foo" f.rewind f.read # => "foo\n" } 

Several candidates for the keyword argument:

• unlink_first: true

• remove_immediately: true

• delete_on_creation: true

• unnamed: true

• nameless: true

• anonymous: true

• named: false

My personal preference would go to anonymous: true, probably followed by linked: false.

I have a minor preference for unnamed: true, but anonymous: true is probably more approachable overall.

I talked with Matz today.
He said anonymous: true is acceptable.