我在使用trap和catch/throw方法时注意到了这种行为，以便更好地理解它们可以/应该如何使用。
在Ruby中，catch和throw方法似乎是成对使用的：

catch(:ctrl_c) do
  trap("SIGINT") { throw :ctrl_c }
  (1.. ).each {|n| print "."; sleep 0.5 }
end

# SIGINT trapped -> throw called -> catch block exits
#   ruby covthrow1p.rb
#   => ........

字符串
或者使用提供给throw方法的第二个参数：

def stop_script
  puts 'CTRL_C seen'
  exit
end

catch(:ctrl_c) do
  trap("SIGINT") { throw :ctrl_c, stop_script }
  (1.. ).each {|n| print "."; sleep 0.5 }
end

# SIGINT trapped -> throw called -> catch executes stop_script & exits block
#   ruby covthrow2p.rb
#   => ......CTRL_C seen

型
如果单独使用throw（naked），只提供key参数，则失败：

def stop_script
  puts 'CTRL_C seen'
  exit
end

trap("SIGINT") { throw :ctrl_c }
(1.. ).each {|n| print "."; sleep 0.5 }

# SIGINT trapped -> throw called -> No catch block -> UncaughtThrowError
#   ruby nkdthrow1p.rb
#   => .......nkdthrow1p.rb:8:in `throw': uncaught throw :ctrl_c (UncaughtThrowError)

型
但是如果使用裸抛出并提供第二个参数，则会成功！

def stop_script
  puts 'CTRL_C seen'
  exit
end

trap("SIGINT") { throw :ctrl_c, stop_script }
(1.. ).each {|n| print "."; sleep 0.5 }

# SIGINT trapped -> throw called -> No catch block -> call stop_script ???
#   ruby nkdthrow2p.rb
#   => ......CTRL_C seen

型
这是预期行为吗？一个执行的工件？一个bug？看起来一般是无害的，但可能会导致混乱的行为。
这些示例是在Windows 10上运行的Ruby 3.2.2上。