[#102652] [Ruby master Bug#17664] Behavior of sockets changed in Ruby 3.0 to non-blocking — ciconia@...
Issue #17664 has been reported by ciconia (Sharon Rosner).
23 messages
2021/02/28
[ruby-core:102434] [Ruby master Feature#7394] Enumerable#find ifnone parameter could be non-callable
From:
keystonelemur@...
Date:
2021-02-10 07:48:48 UTC
List:
ruby-core #102434
Issue #7394 has been updated by baweaver (Brandon Weaver).
I rather like @ioquatix idea here, and was considering making a similar ticket to suggest that `ifnone` does not make much sense when compared to other Ruby APIs.
Would we still consider merging this?
----------------------------------------
Feature #7394: Enumerable#find ifnone parameter could be non-callable
https://bugs.ruby-lang.org/issues/7394#change-90318
* 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: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>