2 ms·
> The most irritating example of this is that if you don't pass enough arguments to a proc object the other parameters get filled in with nil. In my mind this s
by ajuc 15y ago
> The most irritating example of this is that if you don't pass enough arguments to a proc object the other parameters get filled in with nil. In my mind this should throw a type error, but in Ruby it doesn't.
Maybe automate checking this? I don't know Ruby much, but there's .arity method on proc that seems to be apropriate for this.