diff options
author | Alan Wu <XrXr@users.noreply.github.com> | 2019-07-13 12:04:01 -0400 |
---|---|---|
committer | Alan Wu <XrXr@users.noreply.github.com> | 2019-12-21 09:08:52 -0500 |
commit | 85a337f986fe6da99c7f8358f790f17b122b3903 (patch) | |
tree | f5c41137c2db802327cd4c405de7a922cbae7453 /.editorconfig | |
parent | ddb6023d64a8c96348b4e67603753e2916a04f28 (diff) |
Kernel#lambda: return forwarded block as non-lambda proc
Before this commit, Kernel#lambda can't tell the difference between a
directly passed literal block and one passed with an ampersand.
A block passed with an ampersand is semantically speaking already a
non-lambda proc. When Kernel#lambda receives a non-lambda proc, it
should simply return it.
Implementation wise, when the VM calls a method with a literal block, it
places the code for the block on the calling control frame and passes a
pointer (block handler) to the callee. Before this commit, the VM
forwards block arguments by simply forwarding the block handler, which
leaves the slot for block code unused when a control frame forwards its
block argument. I use the vacant space to indicate that a frame has
forwarded its block argument and inspect that in Kernel#lambda to detect
forwarded blocks.
This is a very ad-hoc solution and relies *heavily* on the way block
passing works in the VM. However, it's the most self-contained solution
I have.
[Bug #15620]
Notes
Notes:
Merged: https://github.com/ruby/ruby/pull/2289
Diffstat (limited to '.editorconfig')
0 files changed, 0 insertions, 0 deletions