| Age | Commit message (Collapse) | Author |
|---|
|
https://github.com/ruby/prism/commit/b5e47f5c42
|
|
https://github.com/ruby/prism/commit/5dd57f4b84
|
|
https://github.com/ruby/prism/commit/eabed9f4fd
|
|
When creating the Ruby AST, we were previously allocating Location
objects for every node and every inner location. Instead, this
commit changes it to pack both the start offset and length into a
single u64 and pass that into the nodes. Then, when the locations
are requested via a reader method, we lazily allocate the Location
objects.
https://github.com/ruby/prism/commit/de203dca83
Co-Authored-By: Aaron Patterson <tenderlove@ruby-lang.org>
|
|
https://github.com/ruby/prism/commit/6e69a81737
|
|
* 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/commit/fef0019a25
|
|
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
|
|
|
|
|
