| Age | Commit message (Collapse) | Author |
|
They currently complain that the parent method is not forwarding.
But the actual problem is that these types of arguments simply don't
accept `...`
Fixes [Bug #21927]
https://github.com/ruby/prism/commit/0aa2363331
|
|
https://github.com/ruby/prism/commit/b960079559
|
|
https://github.com/ruby/prism/commit/e3e2b1ed04
|
|
https://github.com/ruby/prism/commit/5b7456c8f6
|
|
https://github.com/ruby/prism/commit/69abcdbb18
|
|
When there are nested capture variables inside of a pattern match
that has an alternation pattern, it is a syntax error. Currently it
only adds a syntax error when it is at the top level of the pattern.
|
|
Fixes [Bug #21661]
https://github.com/ruby/prism/commit/475fa46a82
|
|
Should fail even with `-c` option.
|
|
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
|
|
type. Since a endless method is started with `=`, there was ambiguity here. We have to simply reject these in all cases.
This adds a new error for the following reason:
* `def foo arg = nil` is interpreted as a normal method call with optional `arg` without matching `end`
* `def foo *arg = nil; end` is interpreted as a endless method call that has body `nil` with extraneous `end`
`def foo *arg = nil` is somewhere inbetween and I don't know how to otherwise indicate the error.
Now the second case above also shows the newly added error message.
Fixes [Bug #21623]
https://github.com/ruby/prism/commit/e1910d4492
|
|
https://github.com/ruby/prism/commit/2ddedf650a
|
|
https://github.com/ruby/prism/commit/0d94291416
|
|
https://github.com/ruby/prism/commit/af9047f378
|
|
https://github.com/ruby/prism/commit/a0cc316e91
|
|
https://github.com/ruby/prism/commit/9b7dfcc3e0
|
|
https://github.com/ruby/prism/commit/c80c4d958e
|
|
https://github.com/ruby/prism/commit/193984b760
|
|
https://github.com/ruby/prism/commit/03ca35b3ab
|
|
https://github.com/ruby/prism/commit/483aa89234
|
|
command calls
https://github.com/ruby/prism/commit/d9151b8a82
|
|
A command-call-like `not true` must be rejected after `&&` and `||`.
https://bugs.ruby-lang.org/issues/21337
https://github.com/ruby/prism/commit/0513cf22ad
|
|
of the `ClassNode`. - Part of #2123
https://github.com/ruby/prism/commit/99615b43ac
|
|
This can get triggered even if the list of statements only contains
a single statement. This is necessary to properly support compiling
```ruby
defined? (;a)
defined? (a;)
```
as "expression". Previously these were parsed as statements lists
with single statements in them.
https://github.com/ruby/prism/commit/b63b5d67a9
|
|
https://github.com/ruby/prism/commit/bde8ccc038
|
|
https://github.com/ruby/prism/commit/f734350499
|
|
https://github.com/ruby/prism/commit/9686897290
Notes:
Merged: https://github.com/ruby/ruby/pull/12358
|
|
Partially: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/1ffd693f9b
|
|
Partially: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/a78da01ef6
|
|
Partially: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/2f473b0713
|
|
Partially: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/7be164e0b7
|
|
Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/f1f8776973
|
|
Partially: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/3c01cc7c77
|
|
Partially: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/649ef29c29
|
|
```
❯ ruby --parser=prism --dump=parsetree -e "foo in *1"
ruby: -e:1: syntax error found (SyntaxError)
> 1 | foo in *1
| ^ unexpected integer, expecting end-of-input
2 |
```
|
|
Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/b8f40988ab
|
|
Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/396c6d4340
|
|
Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/27f13fabc6
|
|
Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/1388ca389e
|
|
Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/b1c2f323f9
|
|
Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/8353be1dfe
|
|
Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/9c0ef71449
|
|
Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/480897eccf
|
|
Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/75d1bde6cc
|
|
Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/d1570f2e06
|
|
Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/145ae8f993
|
|
Its `exception` field was renamed to `reference` in #1204 but the
documentation was not updated.
https://github.com/ruby/prism/commit/a477607ba2
|
|
https://github.com/ruby/prism/commit/023e894b74
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11753
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11741
|
|
https://github.com/ruby/prism/commit/fd58d6a9ea
|