[Solved] Find the problem in this Ruby code snippet: t = Thread.new { puts "Hello" } t.join() puts t.value — Ans: Thread does not return a value by default, so t.value is nil. | Ruby

Ruby - Concurrent Programming

Find the problem in this Ruby code snippet:

t = Thread.new { puts "Hello" }
t.join()
puts t.value

AThread.new requires a return statement inside the block.

BCalling t.value before join causes an error.

CThread does not return a value by default, so t.value is nil.

Dt.join() should be called after accessing t.value.

Step-by-Step Solution

Solution:

Step 1: Understand thread return values
Thread returns the last expression value from its block. Here, puts "Hello" returns nil.
Step 2: Analyze t.value usage
Calling t.value returns nil because puts returns nil, not an error.
Final Answer:
Thread does not return a value by default, so t.value is nil. -> Option C
Quick Check:
Thread value = last expression result (nil here) [OK]

Quick Trick: Thread value is last block expression result, often nil with puts [OK]

Common Mistakes:

Master "Concurrent Programming" in Ruby

9 interactive learning modes - each teaches the same concept differently

More Ruby Quizzes

Find the problem in this Ruby code snippet: