This should be squashed when merged. Let us know when you're satisfied 😀

@ahorek travis is pretty unhappy with some Enumerator arity errors. Perhaps something in this PR changed some arity checking?

yeah, there're still some cases that don't work as expected, I'll let you know when it's ready

@ahorek ok. Thanks for fixing this... It has been an annoyance that the format was old

@enebo @headius ready for review!

@ahorek looks pretty straight-forward...just merged it

This appears to be breaking at least one spec that expects no method name in the message:

108)
Thread.each_caller_location doesn't accept positional and keyword arguments ERROR
Expected ArgumentError (wrong number of arguments (given 2, expected 0))
but got: ArgumentError (`each_caller_location': wrong number of arguments (given 2, expected 0))

We probably should just drop the method name.