raise shorthand

[chriseppstein]

Ruby allows raise <ExceptionType>, <message> which it then translates into raise <ExceptionType>.new(<message>).

I think most people prefer the former, but my project prefers the latter. I think there should be a cop that enforces one or the other and which form should be configurable.

[bbatsov]

Sure, that makes sense.

[bbatsov]

Btw, what about the scenario when raise is called with 3 arguments - raise ExceptionClass, message, backtrace? AFAIK you cannot pass the backtrace to the Exception constructor, so that would introduce an inconsistency. Or I just might be missing something.

[jonas054]

I guess the specific exception class being raised could take a backtrace argument and call set_backtrace internally, but RuboCop can't be expected to know that. So I say you should allow raise with 3 arguments, or possibly have a configuration parameter called AllowRaiseWithThreeArguments or something, trueby default.

[chriseppstein]

That's fine. It's a very rare thing to do. We use set_backtrace and the single argument version.