ruby.git/lib/prism/translation/parser/compiler.rb, branch v4.0.4

[ruby/prism] Add equal_loc to call nodes

2025-10-30T13:06:09+00:00

In the case of attribute writes, there are use cases where you want
to know the location of the = sign. (Internally we actually need
this for translation to the writequark AST.)

https://github.com/ruby/prism/commit/bfc798a7ec

[ruby/prism] [DOC] Specify markdown mode to RDoc

2025-05-29T04:45:58+00:00

https://github.com/ruby/prism/commit/12af4e144e

[ruby/prism] Fix parsing rescued exception via indexed assignment

2025-04-12T17:43:57+00:00

Given this code

```ruby
begin
  raise '42'
rescue => A[]
end
```

Prism fails with this backtrace

```
Error: test_unparser/corpus/literal/rescue.txt(Prism::ParserTest): NoMethodError: undefined method `arguments' for nil
prism/lib/prism/translation/parser/compiler.rb:1055:in `visit_index_target_node'
prism/lib/prism/node.rb:9636:in `accept'
prism/lib/prism/compiler.rb:30:in `visit'
prism/lib/prism/translation/parser/compiler.rb:218:in `visit_begin_node'
```

Seems like

```diff
-            visit_all(node.arguments.arguments),
+            visit_all(node.arguments&.arguments || []),
```

fixes the problem.

https://github.com/ruby/prism/commit/76d01aeb6c

[ruby/prism] Fix parser translator when splatting in pattern matching pin

2025-04-02T20:51:54+00:00

Because it ends up treating it as a local variable, and `a.x`
is not a valid local variable name.

I'm not big on pattern matching, but conceptually it makes sense to me
to treat anything inside ^() to not be
pattern matching syntax?

https://github.com/ruby/prism/commit/80dbd85c45

[ruby/prism] Fix parser translator when pinning hash with string keys

2025-03-30T17:24:05+00:00

`StringNode` and `SymbolNode` don't have the same shape
(`content` vs `value`) and that wasn't handled.

I believe the logic for the common case can be reused.
I simply left the special handling for implicit nodes in pattern matching
and fall through otherwise.

NOTE: patterns.txt is not actually tested at the moment,
because it contains syntax that `parser` mistakenly rejects.
But I checked manually that this doesn't introduce other failures.
https://github.com/whitequark/parser/pull/1060

https://github.com/ruby/prism/commit/55adfaa895

[ruby/prism] Accept a newline after the defined? keyword

2025-03-30T17:22:41+00:00

[Bug #21197]

https://github.com/ruby/prism/commit/22be955ce9

Fix up merge conflicts for prism sync

2025-03-18T17:36:53+00:00

[ruby/prism] Only unnest parser mlhs nodes when no rest argument is provided

2025-03-18T17:36:53+00:00

```
(a,), = []

PARSER====================
s(:masgn,
  s(:mlhs,
    s(:mlhs,
      s(:lvasgn, :a))),
  s(:array))
PRISM====================
s(:masgn,
  s(:mlhs,
    s(:lvasgn, :a)),
  s(:array))
```

https://github.com/ruby/prism/commit/8aa1f4690e

[ruby/prism] Fix parser translator multiline interpolated symbols

2025-03-18T17:36:53+00:00

In https://github.com/ruby/prism/commit/26370079291a420c6b2b7be5cdbd5c609da62f21 I added tests but didn't modify them correctly

https://github.com/ruby/prism/commit/de021e74de

[ruby/prism] Further refine string handling in the parser translator

2025-03-18T17:36:53+00:00

Mostly around newlines and line continuation.
* percent arrays need special backslash handling in the ast
* Fix offset issue for heredocs with many line continuations (used wrong variable as index access)
* More refined rules on when to simplify string tokens
* Handle line continuations in squiggly heredocs
* Correctly dedent squiggly heredocs with interpolation
* Consider `':foo:` and `%s[foo]` to not be interpolation

https://github.com/ruby/prism/commit/4edfe9d981