summaryrefslogtreecommitdiff
path: root/include/ruby
diff options
context:
space:
mode:
authorJeremy Evans <code@jeremyevans.net>2023-11-06 12:08:03 -0800
committerJeremy Evans <code@jeremyevans.net>2023-12-07 11:27:55 -0800
commitc70c1d2a9592bcea916500eb16ae58f6de4b9a3f (patch)
tree4a37dead56b26bf8f79270eac8652378b0a310e4 /include/ruby
parent40a2afd08fe1b921f1052b29031abfa1869e0557 (diff)
Eliminate array allocation for f(1, *a, &lvar) and f(1, *a, &@iv)
Due to how the compiler works, while f(*a, &lvar) and f(*a, &@iv) do not allocate an array, but f(1, *a, &lvar) and f(1, *a, &@iv) do. It's probably possible to fix this in the compiler, but seems easiest to fix this in the peephole optimizer. Eliminating this array allocation is as safe as the current elimination of the array allocation for f(*a, &lvar) and f(*a, &@iv).
Diffstat (limited to 'include/ruby')
0 files changed, 0 insertions, 0 deletions