[#109095] [Ruby master Misc#18888] Migrate ruby-lang.org mail services to Google Domains and Google Workspace — "shugo (Shugo Maeda)" <noreply@...>
Issue #18888 has been reported by shugo (Shugo Maeda).
16 messages
2022/06/30
[ruby-core:108992] [Ruby master Feature#18831] Block argument to `yield`
From:
"mame (Yusuke Endoh)" <noreply@...>
Date:
2022-06-18 03:12:21 UTC
List:
ruby-core #108992
Issue #18831 has been updated by mame (Yusuke Endoh). mame (Yusuke Endoh) wrote in #note-2: > @matz was not positive to change it. I forgot to add the reason why he was not positive. @matz said he no longer want to make `yield` so useful. He recommends an explicit `Proc#call` with a block parameter instead of an implicit block call by `yield`, especially it passes complex arguments like a block. ``` def foo(&b) b.call(1, 2, 3) do end end ``` ---------------------------------------- Feature #18831: Block argument to `yield` https://bugs.ruby-lang.org/issues/18831#change-98103 * Author: nobu (Nobuyoshi Nakada) * Status: Open * Priority: Normal ---------------------------------------- Block argument to `yield` is a syntax error. This is because there was previously no way to receive a given block in the yielded block. However `do |&block|` has been introduced since 1.8.7. Why is it prohibited still now? https://github.com/nobu/ruby/tree/blockarg-yield -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>