ruby.git/test/prism/fixtures, branch v3_3_11

Revert all of commits after Prism 0.19.0 release

2023-12-16T03:08:51+00:00

  We should bundle released version of Prism for Ruby 3.3.0

[ruby/prism] Invalid pinned locals in pattern matching

2023-12-15T15:03:49+00:00

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

[ruby/prism] Fix parse result for nesting pattern matching

2023-12-14T18:54:46+00:00

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

[ruby/prism] Handle a non-interpolated dsym spanning a heredoc

2023-12-11T16:34:41+00:00

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

[ruby/prism] Fix to parse a (endless-)range with binary operators

2023-12-11T13:34:48+00:00

Fix https://github.com/ruby/prism/pull/2022
Fix https://github.com/ruby/prism/pull/2030

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

[ruby/prism] Fix defined with new line

2023-12-05T20:47:22+00:00

It's possible to write the following and have it be valid Ruby:

```
defined?("foo"
)
```

But Prism wasn't taking the new line into account. This adds an
`accept1` for a `PM_TOKEN_NEWLINE` to account for this. I've also
updated the fixtures and snapshots to test this.

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

[ruby/prism] Add test cases

2023-12-05T15:16:42+00:00

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

[ruby/prism] Fix some corner cases

2023-12-05T15:16:41+00:00

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

[ruby/prism] Fix to parse command-style method calls more correctly

2023-12-05T15:16:40+00:00

Fix https://github.com/ruby/prism/pull/1468
Fix https://github.com/ruby/prism/pull/1575

To decide command-style method calls are allowed, this introduce a new
parameter `accepts_command_call` to `parse_expression` and some
functions.

Although one think this can be solved by operator precedence, it is
hard or impossible, because the precedence of command-style calls is skewed
(e.g. `! bar 1 ` is accepted, but `foo = ! bar 1` is rejected.)

One of the most complex examples is that:
(1) even though `foo = bar = baz 1` and `foo, bar = baz 1` is accepted,
(2) `foo, bar = baz = fuzz 1` is rejected.
To implement this behavior, this introduces a new binding power
`PM_BINDING_POWER_MULTI_ASSIGNMENT` and uses it for distinguish which single
assignments or multi assignments at their RHS.

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

[ruby/prism] Fix parsing heredoc ends

2023-12-01T20:10:58+00:00

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