From: ko1@... Date: 2020-01-16T08:12:28+00:00 Subject: [ruby-core:96900] [Ruby master Feature#15973] Let Kernel#lambda always return a lambda Issue #15973 has been updated by ko1 (Koichi Sasada). Quote from today's devmeeting. Discussion: * Proposing to deprecate `lambda(&block)` (`lambda` call with `Proc` object as block) * Benefits of obsoleting `lambda`? * Simplify for new Ruby developers. (no duplicated syntax.) * Suspend for short term (for years) * Don't want more incompatibilities just after Ruby 2.7 * Migration pass to deprecate `lambda(&block)`. 1. Print warning at 3.0. (No compatibility layer.) * ���The lambda call is meaningless. Delete it.��� * ���Delete meaningless lambda��� 3. Raises error at 3.1 (or 3.2, ...) Conclusion: * `lambda(&b)` will be prohibited. * Print warning at 3.0. (No compatibility layer.) * Raises error at 3.1 (or 3.2, ...) ---------------------------------------- Feature #15973: Let Kernel#lambda always return a lambda https://bugs.ruby-lang.org/issues/15973#change-83917 * Author: alanwu (Alan Wu) * Status: Assigned * Priority: Normal * Assignee: matz (Yukihiro Matsumoto) * Target version: 2.8 ---------------------------------------- When Kernel#lambda receives a Proc that is not a lambda, it returns it without modification. l propose to change `Kernel#lambda` so it always returns a lambda. Calling a method called lambda and having it do nothing in effect is not very intuitive. https://github.com/ruby/ruby/pull/2262 Judging from marcandre's investigation here: https://bugs.ruby-lang.org/issues/15620#note-1, changing the behavior should not cause much breakage, if any. This also happens to fix [Bug #15620] -- https://bugs.ruby-lang.org/ Unsubscribe: