ruby.git/test/prism/errors_test.rb, 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] Add an error for `in` keyword in arguments

2023-12-15T13:25:54+00:00

Fix https://github.com/ruby/prism/pull/2026

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

[ruby/prism] Make equality operators non-associative

2023-12-14T16:39:05+00:00

Fix https://github.com/ruby/prism/pull/2073

https://github.com/ruby/prism/commit/0f747d9240

[ruby/prism] Update tests and snapshots

2023-12-12T13:05:09+00:00

https://github.com/ruby/prism/commit/0663e2bcfa

[ruby/prism] Fix parsing unterminated empty string `"`

2023-12-11T13:36:37+00:00

Fix https://github.com/ruby/prism/pull/2034

https://github.com/ruby/prism/commit/8280e577fa

[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: escape newline

2023-12-10T03:06:36+00:00

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

[ruby/prism] Add necessary encoding flags for symbols and regex

2023-12-08T18:59:52+00:00

This doesn't actually fix the encodings for symbols and regex,
unfortunately. But I wanted to get this change in because it is
the last AST change we're going to make before 3.3 is released.

So, if consumers want, they can start to check these flags to
determine the encoding, even though it will be wrong. Then once we
actually set them correctly, everything should work.

https://github.com/ruby/prism/commit/9b35f7e891

[ruby/prism] More closely match CRuby error messages

2023-12-08T14:34:34+00:00

https://github.com/ruby/prism/commit/1ed07a0c6d

[ruby/prism] Emit error for constant assignments in defs

2023-12-06T22:15:16+00:00

https://github.com/ruby/prism/commit/864b06f90e