ruby.git/test/ruby/test_lambda.rb, branch v3_2_11 The Ruby Programming Language test/ruby/test_lambda.rb: Remove "warning: assigned but unused variable" 2021-04-04T06:26:09+00:00 Yusuke Endoh mame@ruby-lang.org 2021-04-04T06:26:09+00:00 2fcae4f90ab08ae06c28c4aa0989ee06d97f0536 






fix return from orphan Proc in lambda
2021-04-02T00:25:33+00:00

Koichi Sasada
ko1@atdot.net

2021-04-01T17:28:00+00:00

ecfa8dcdbaf60cbe878389439de9ac94bc82e034

A "return" statement in a Proc in a lambda like:
  `lambda{ proc{ return }.call }`
should return outer lambda block. However, the inner Proc can become
orphan Proc from the lambda block. This "return" escape outer-scope
like method, but this behavior was decieded as a bug.
[Bug #17105]

This patch raises LocalJumpError by checking the proc is orphan or
not from lambda blocks before escaping by "return".

Most of tests are written by Jeremy Evans
https://github.com/ruby/ruby/pull/4223





A "return" statement in a Proc in a lambda like:
  `lambda{ proc{ return }.call }`
should return outer lambda block. However, the inner Proc can become
orphan Proc from the lambda block. This "return" escape outer-scope
like method, but this behavior was decieded as a bug.
[Bug #17105]

This patch raises LocalJumpError by checking the proc is orphan or
not from lambda blocks before escaping by "return".

Most of tests are written by Jeremy Evans
https://github.com/ruby/ruby/pull/4223







test/ruby/test_lambda.rb: prevent lambda(&proc_block) warnings
2020-12-12T14:11:47+00:00

Yusuke Endoh
mame@ruby-lang.org

2020-12-12T14:11:47+00:00

efbef729b2aee13241e6f7606f90d407f4530df8












Disable deprecation warning by the default [Feature #16345]
2020-09-25T00:50:33+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2020-08-31T05:58:31+00:00

996af2ce086249e904b2ce95ab2fcd1de7d757be

And `-w` option turns it on.





And `-w` option turns it on.







Warn when passing a non-literal block to Kernel#lambda
2020-06-11T14:30:48+00:00

Jeremy Evans
code@jeremyevans.net

2020-06-11T00:50:35+00:00

2188d6d160d3ba82432c87277310a4d417e136d5

Implements [Feature #15973]





Implements [Feature #15973]







Kernel#lambda: return forwarded block as non-lambda proc
2019-12-21T14:08:52+00:00

Alan Wu
XrXr@users.noreply.github.com

2019-07-13T16:04:01+00:00

85a337f986fe6da99c7f8358f790f17b122b3903

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]





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]







add tests for orphan/not-orphan proc/lambda.
2019-07-15T05:17:27+00:00

Tanaka Akira
akr@fsij.org

2019-07-15T05:17:27+00:00

e4c1b199961cc5fa34c02b2225bbc14b75259fd2












add tests for "break" in lambda.
2019-07-15T03:59:53+00:00

Tanaka Akira
akr@fsij.org

2019-07-15T03:59:53+00:00

bd494ae79b18e260b0123bf40ddc1c694d7b25b8












vm_args.c: arity check of lambda
2017-03-19T01:11:12+00:00

nobu
nobu@b2dd03c8-39d4-4d8f-98ff-823fe69b080e

2017-03-19T01:11:12+00:00

976becf7eb18aa1592c703ac4d86a2cf9dfa701e

* vm_eval.c (rb_yield_lambda): new function which yields an array
  to a proc and splat to a lambda.  mainly for Enumerable only.

* vm_args.c (setup_parameters_complex): remove special lambda
  splatting for [Bug #9605].  [ruby-core:77065] [Bug #12705]

* vm_insnhelper.c (vm_callee_setup_block_arg): ditto.

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@58019 b2dd03c8-39d4-4d8f-98ff-823fe69b080e





* vm_eval.c (rb_yield_lambda): new function which yields an array
  to a proc and splat to a lambda.  mainly for Enumerable only.

* vm_args.c (setup_parameters_complex): remove special lambda
  splatting for [Bug #9605].  [ruby-core:77065] [Bug #12705]

* vm_insnhelper.c (vm_callee_setup_block_arg): ditto.

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@58019 b2dd03c8-39d4-4d8f-98ff-823fe69b080e







test_lambda.rb: remove duplcate tests
2017-03-18T15:58:13+00:00

nobu
nobu@b2dd03c8-39d4-4d8f-98ff-823fe69b080e

2017-03-18T15:58:13+00:00

a9d575e507e1ce181ed71b9a7d4c3ad4f2f23e59

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@58018 b2dd03c8-39d4-4d8f-98ff-823fe69b080e





git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@58018 b2dd03c8-39d4-4d8f-98ff-823fe69b080e