[#66126] Creation/Conversion methods/functions table for Ruby types — SASADA Koichi <ko1@...>
Hi,
5 messages
2014/11/07
[#66248] [ruby-trunk - Feature #10423] [PATCH] opt_str_lit*: avoid literal string allocations — normalperson@...
Issue #10423 has been updated by Eric Wong.
3 messages
2014/11/13
[#66595] [ruby-trunk - Bug #10557] [Open] Block not given when the argument is a string — bartosz@...
Issue #10557 has been reported by Bartosz Kopinski.
3 messages
2014/11/30
[ruby-core:66260] [ruby-trunk - Feature #10506] [Open] Imprve Enumerator.any? behavior
From:
ts@...
Date:
2014-11-13 12:40:33 UTC
List:
ruby-core #66260
Issue #10506 has been reported by Thomas Sevestre.
----------------------------------------
Feature #10506: Imprve Enumerator.any? behavior
https://bugs.ruby-lang.org/issues/10506
* Author: Thomas Sevestre
* Status: Open
* Priority: Normal
* Assignee:
* Category:
* Target version:
----------------------------------------
IMHO the API `Enumerable.any?` behavior could be improved in the following manner:
any? { |obj| block } → true or false
any? → an_enumerator
This would allow to do things like
[].any?.with_index { |obj, index| }
And it would be more consistent with collect and other Enumerable functions:
collect { |obj| block } → array
collect → an_enumerator
--
https://bugs.ruby-lang.org/