| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
I don't prefer this style, but it appears that a plurality of syntax
error messages between with un-capitalized messages in CRuby, so
we'll go with that for consistency, for now.
https://github.com/ruby/prism/commit/b02df68954
|
|
|
|
|
|
| |
Fix https://github.com/ruby/prism/pull/1920
https://github.com/ruby/prism/commit/ee8e03bac7
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix https://github.com/ruby/prism/pull/1925
Fix https://github.com/ruby/prism/pull/1927
Previously pm_call_node_index_p does not check about a block argument
correctly and is not used in parse_write to check an index call node.
This commit fixes these problems.
https://github.com/ruby/prism/commit/92bab044ff
|
|
|
|
|
|
| |
Follow up the ruby/ruby#8917 change.
https://github.com/ruby/prism/commit/f6bac4d3bf
|
|
|
|
|
|
| |
Fix https://github.com/ruby/prism/pull/1828
https://github.com/ruby/prism/commit/22c0640e48
|
|
|
|
|
|
| |
Fix https://github.com/ruby/prism/pull/1547
https://github.com/ruby/prism/commit/cdb643aeab
|
|
|
|
|
|
|
|
| |
* The same order as in source code.
* CallOrWriteNode, CallOperatorWriteNode, CallAndWriteNode already have
the correct order so it was also inconsistent with them.
https://github.com/ruby/prism/commit/4434e4bc22
|
|
|
|
|
|
|
|
|
|
| |
(https://github.com/ruby/prism/pull/1837)
Fix https://github.com/ruby/prism/pull/1829
https://github.com/ruby/prism/commit/90b0b1974c
Co-authored-by: Kevin Newton <kddnewton@gmail.com>
|
|
|
|
|
|
| |
(https://github.com/ruby/prism/pull/1899)
https://github.com/ruby/prism/commit/1b41c2d56c
|
|
|
|
|
|
|
|
| |
(https://github.com/ruby/prism/pull/1878)
Fix https://github.com/ruby/prism/pull/1832
https://github.com/ruby/prism/commit/060bcc81a8
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(https://github.com/ruby/prism/pull/1796)
Previously, we only supported error messages that were constant
strings. This works for the most part, but there are some times
where we want to include some part of the source in the error
message to make it better.
For example, instead of "Token is reserved" it's better to write
"_1 is reserved".
To do this, we now support allocating error messages at runtime
that are built around format strings.
https://github.com/ruby/prism/commit/7e6aa17deb
|
|
|
|
|
|
| |
(https://github.com/ruby/prism/pull/1801)
https://github.com/ruby/prism/commit/4c1391ea56
|
|
|
|
|
|
| |
(https://github.com/ruby/prism/pull/1797)
https://github.com/ruby/prism/commit/c13165e6aa
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(https://github.com/ruby/prism/pull/1882)
* Fix parsing `...` in arguments
Fix https://github.com/ruby/prism/pull/1830
Fix https://github.com/ruby/prism/pull/1831
* Rename the constant name to PM_ERR_ARGUMENT_FORWARDING_UNBOUND
https://github.com/ruby/prism/pull/1882#discussion_r1398461156
https://github.com/ruby/prism/commit/519653aec2
|
|
|
|
| |
https://github.com/ruby/prism/commit/f1d56da58f
|
| |
|
|
|
|
| |
https://github.com/ruby/prism/commit/d60948bac3
|
|
|
|
|
|
| |
They are corresponding to `arg_value` in `parse.y`.
https://github.com/ruby/prism/commit/a4a4834e0d
|
|
|
|
|
|
| |
They are corresponding to `arg_value` in `parse.y`.
https://github.com/ruby/prism/commit/a4a4834e0d
|
|
|
|
| |
https://github.com/ruby/prism/commit/d60948bac3
|
|
|
|
|
|
| |
They are corresponding to `arg_value` in `parse.y`.
https://github.com/ruby/prism/commit/a4a4834e0d
|
|
|
|
| |
https://github.com/ruby/prism/commit/37fad74134
|
|
|
|
| |
https://github.com/ruby/prism/commit/231e965124
|
|
|
|
| |
https://github.com/ruby/prism/commit/b7850f2d30
|
|
|
|
| |
https://github.com/ruby/prism/commit/ec419422f8
|
|
|
|
|
|
| |
RequiredKeywordParameterNode
https://github.com/ruby/prism/commit/c31f61e898
|
|
|
|
|
|
|
|
| |
Prior to this commit, KeywordParameterNode included both optional
and required keywords. With this commit, it is split in two, with
`OptionalKeywordParameterNode`s no longer having a value field.
https://github.com/ruby/prism/commit/89084d9af4
|
|
|
|
| |
https://github.com/ruby/prism/commit/e60240d54b
|
|
|
|
|
|
|
|
|
| |
Method calls with keyword splat args compile differently than
without since they merge the keyword arg hash with the keyword splat
hash. We know this information at parse time, so can set a flag
which the compiler can use.
https://github.com/ruby/prism/commit/e5f8a9a3cd
|
|
|
|
| |
https://github.com/ruby/prism/commit/e8114a786a
|
|
|
|
| |
https://github.com/ruby/prism/commit/11255f636e
|
|
|
|
| |
https://github.com/ruby/prism/commit/e16531650d
|
|
|
|
| |
https://github.com/ruby/prism/commit/66248ac2f6
|
|
|
|
| |
https://github.com/ruby/prism/commit/c3438aabea
|
|
|
|
| |
https://github.com/ruby/prism/commit/e100c6b8ae
|
|
|
|
| |
https://github.com/ruby/prism/commit/53efaf252d
|
|
|
|
| |
* https://github.com/ruby/prism/pull/1533
|
|
|
|
| |
https://github.com/ruby/prism/commit/bf43006d0a
|
|
|
|
| |
https://github.com/ruby/prism/commit/0326ba6775
|
|
|
|
| |
https://github.com/ruby/prism/commit/f86bff6dd7
|
| |
|
|
|