tomoya ishida

`.. * x` is parsed as `(something..) * x` `.. . x` is parsed as `(something..). x` ```ruby a b .. * x a b .. . x a =...

These codes are accepted in Prism. ```ruby ( + ( * ) ) ( a ( * ) ) ( 1 + ( * ) ) ( .. ( *...

Prism accepts MultiTargetNode inside `*()` where Ruby rejects ```ruby *(*) = 1 *(a, *b) = 1 for *(a, b) in a; end ```

MultiWrite or Splat assign like this ```ruby a = *b (*) = a *a = b ``` are accepted in these places in Prism, but Ruby rejects it. ```ruby +...

Ruby rejects empty group name in regexp `/(?<>)/` but prism accepts it

1

```ruby eval "/(?)/" # group name is empty: /(?)/ (SyntaxError) eval "/(?)/" # group name is empty: /(?)/ (SyntaxError) eval "/(?)/" # syntax ok. group name is "\n" Prism.parse "/(?)/"...

Improve error message of #958 ``` irb(main):001> measure = 1 undefined method `extract_ruby_args=' for module IRB::Command (NoMethodError) IRB::Command.extract_ruby_args = 1 ^^^^^^^^^^^^^^^^^^^^ Maybe IRB bug! ``` This is not a bug....

Hash#inspect with colon style

2

Implements https://bugs.ruby-lang.org/issues/20433#note-7 Change Hash#inspect to use colon style if the key is a symbol. ```ruby puts({a!: 1, "" => 1, "a=": 1, 42 => 1}.inspect) # => {a!: 1, ""...

Allow assigning to local variable conflicting with command name

1

`n = 1` `n += 1` `n **= 1` `n &&= 1` will be a ruby expression, not a shorthand of `next` command. ```ruby (ruby) n = 1 1 (ruby)...

Fix irb_test prompt assertion failure

1

After changing IRB's behavior with TERM=dumb in https://github.com/ruby/irb/pull/907, `test_irb_command_switches_console_to_irb` and `test_irb_console_config_activates_irb` began failing. This pull request fixes it. With a workaround https://github.com/ruby/irb/pull/943, test does not fail now. ## Description As...

Fixes this bug ```ruby module Mod1 module Sub end end module Mod2 include Mod1 end module Mod3 include Mod2 include Sub # 'Mod1::Sub' is included, but RDoc thinks unknown constant...