Style/RaiseArgs autocorrection produces syntactically invalid Ruby code.

[patbl]

Expected behavior

Style/RaiseArgs autocorrection produces syntactically valid Ruby code.

Actual behavior

Style/RaiseArgs autocorrection produces syntactically invalid Ruby code.

Steps to reproduce the problem

[23:00:21] ~/Documents  ➜ cat lol.rb
false || raise(RuntimeError.new('lol'))
[23:00:48] ~/Documents  ➜ rubocop --only Style/RaiseArgs --auto-correct lol.rb
Inspecting 1 file
E

Offenses:

lol.rb:1:10: C: [Corrected] Style/RaiseArgs: Provide an exception class and message as arguments to raise.
false || raise(RuntimeError.new('lol'))
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
lol.rb:1:16: E: Lint/Syntax: unexpected token tCONSTANT
(Using Ruby 2.2 parser; configure using TargetRubyVersion parameter, under AllCops)
false || raise RuntimeError, 'lol'
               ^^^^^^^^^^^^
lol.rb:1:35: E: Lint/Syntax: unexpected token tNL
(Using Ruby 2.2 parser; configure using TargetRubyVersion parameter, under AllCops)
false || raise RuntimeError, 'lol' ...


1 file inspected, 3 offenses detected, 1 offense corrected
[23:00:57] ~/Documents  ➜ ruby -c lol.rb
lol.rb:1: syntax error, unexpected tCONSTANT, expecting do or '{' or '('
false || raise RuntimeError, 'lol'
lol.rb:1: syntax error, unexpected '\n', expecting '.' or &. or :: or '['

RuboCop version

[22:59:48] ~/Documents  ➜ rubocop -V
0.63.1 (using Parser 2.5.3.0, running on ruby 2.6.0 x86_64-darwin17)

[Drenmi]

Thanks for the report @patbl! I have opened a PR with a fix in #6758. The fix will be shipped as part of a bugfix release sometime within the next couple weeks.