File.open with block (auto-close) in Ruby - Step-by-Step Execution

Concept Flow - File.open with block (auto-close)

Call File.open with block

↓

Open file resource

↓

Execute block with file

↓

Block finishes

↓

File auto-closed

↓

End

The file is opened, the block runs using the file, then the file is automatically closed after the block ends.

Execution Sample

Ruby

File.open('example.txt', 'w') do |file|
  file.puts 'Hello, world!'
end

Open a file for writing, write a line, then automatically close the file.

Execution Table

Step	Action	File State	Block Execution	File Closed?
1	Call File.open with block	File opened for writing	Block not started	No
2	Enter block with file object	File open	Inside block: write 'Hello, world!'	No
3	Block finishes	File open	Block ends	No
4	File auto-closed after block	File closed	Block exited	Yes

💡 Block ends, so file is automatically closed by Ruby.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
file	nil	File object (open)	File object (open)	File object (open)	File object (closed)

Key Moments - 3 Insights

Why don't we need to call file.close explicitly?

Because Ruby automatically closes the file after the block ends, as shown in step 4 of the execution_table.

What happens if an error occurs inside the block?

Ruby still ensures the file is closed after the block finishes or errors out, preventing resource leaks.

Can we use the file object outside the block?

No, the file object is only valid inside the block; after the block, the file is closed and the object should not be used.

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the file actually closed?

A Step 2

B Step 3

C Step 4

D Step 1

💡 Hint

Check the 'File Closed?' column in the execution_table.

According to variable_tracker, what is the state of 'file' after step 3?

A nil

B File object (open)

C File object (closed)

D Undefined

💡 Hint

Look at the 'file' row and the 'After Step 3' column in variable_tracker.

If we remove the block and call File.open without a block, what must we do manually?

A Call file.close explicitly

B Nothing, file auto-closes anyway

C Call file.open again

D Use a different method

💡 Hint

Recall that auto-closing happens only with a block, see key_moments about explicit close.

Concept Snapshot

File.open with block syntax:
File.open('filename', 'mode') do |file|
  # use file here
end

The file is opened, the block runs, then the file is automatically closed.
No need to call file.close manually.
Safe and clean resource management.

Full Transcript

This example shows how Ruby's File.open method works with a block. When you call File.open with a block, Ruby opens the file and passes the file object into the block. Inside the block, you can read from or write to the file. After the block finishes, Ruby automatically closes the file for you. This means you don't have to remember to close the file yourself, which helps avoid mistakes and resource leaks. The execution table shows the steps: opening the file, running the block, then closing the file. The variable tracker shows the file object state changing from open to closed. Remember, the file object is only valid inside the block. If you open a file without a block, you must close it manually.