From: keystonelemur@... Date: 2021-02-10T07:53:06+00:00 Subject: [ruby-core:102435] [Ruby master Feature#7394] Enumerable#find ifnone parameter could be non-callable Issue #7394 has been updated by baweaver (Brandon Weaver). A second argument, however, could be made that `find_index` provides a different API: ```ruby (1..100).find_index(50) ``` ...in which we have a similar API for predicate methods (`any?`),`grep`, and other `Enumerable` methods. I could see cases for both, but the original proposed in this thread would make the most sense given the current API to avoid breakage. ---------------------------------------- Feature #7394: Enumerable#find ifnone parameter could be non-callable https://bugs.ruby-lang.org/issues/7394#change-90319 * Author: zzak (Zachary Scott) * Status: Assigned * Priority: Normal * Assignee: nobu (Nobuyoshi Nakada) ---------------------------------------- from github: https://github.com/ruby/ruby/pull/186 In trunk the `Enumerable#find` method `ifnone` parameter has to be callable or `nil`. I found that sometimes I want to return a simple value without wrapping it in a proc. This pull request adds support for non-callable defaults when no items match. ```ruby a = [1, 2, 3] ``` The current behavior ```ruby a.find(proc { :foo }) { |x| x > 3 } #=> :foo ``` With patch ```ruby a.find(0) { |x| x > 3 } #=> 0 ``` ---Files-------------------------------- enumerable_find_noncallable.patch (3.45 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: