Issue #3916 has been updated by drbrain (Eric Hodel).


There are no priorities for warnings at present, so any code using warnings would need to be updated to take advantage of the feature, breaking backwards compatibility.

Existing uses of #warn could be set as "lowest priority" which makes the feature not very useful since only new code will opt in, and the exception will only be useful when ruby is run with -d, which is rare.
----------------------------------------
Feature #3916: Add flag to ruby to make warnings fatal.
https://bugs.ruby-lang.org/issues/3916#change-24962

Author: docwhat (Christian Höltje)
Status: Assigned
Priority: Normal
Assignee: matz (Yukihiro Matsumoto)
Category: core
Target version: 


=begin
 I have a feature request: Please add a flag to the ruby command line to make warnings fatal.
 
 It would be really handy when debugging and testing to make warnings fatal.
 
 It's not always obvious what bit of code is causing the code that has the warning to execute.  Having a full exception style trace back is very handy.
 
 In addition, if you're doing tests, it would be good to have it raise an exception if a warning is fired.  See http://stackoverflow.com/questions/660737/can-you-ask-ruby-to-treat-warnings-as-errors for an example.
 
 Thanks!
=end



-- 
http://bugs.ruby-lang.org/