ruby.git/lib/prism/translation/parser, branch v4.0.2

[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] Reject some cases with `return` and command calls

2025-09-11T15:55:55+00:00

The same also applies to `break`/`next`.

https://bugs.ruby-lang.org/issues/21540

https://github.com/ruby/prism/commit/3a38b192e3

[ruby/prism] Be more defensive in the parser translator lexer

2025-08-14T15:42:33+00:00

Generally I have been good about safely accessing the tokens but failed
to properly guard against no tokens in places
where it could theoretically happen through invalid syntax.

I added a test case for one occurance, other changes are theoretical only.

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

[ruby/prism] Fix parser translator with trailing backslash in `%W` /`%I` array

2025-06-30T12:32:31+00:00

https://docs.ruby-lang.org/en/master/syntax/literals_rdoc.html#label-25w+and+-25W-3A+String-Array+Literals
> %W allow escape sequences described in Escape Sequences. However the continuation line  is not usable because it is interpreted as the escaped newline described above.

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

[ruby/prism] Fix parser translator during string escaping with invalid utf-8

2025-06-11T18:07:43+00:00

Instead, prefer `scan_byte` over `get_byte` since that already returns the byte as an integer, sidestepping conversion issues.

Fixes https://github.com/ruby/prism/issues/3582

https://github.com/ruby/prism/commit/7f3008b2b5

[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