[#104307] Float truncate — Eustáquio Rangel <eustaquiorangel@...>
Hi!
4 messages
2021/06/16
[ruby-core:104286] [Ruby master Feature#17838] `Set#intersect?` and enumerables
From:
merch-redmine@...
Date:
2021-06-15 18:13:23 UTC
List:
ruby-core #104286
Issue #17838 has been updated by jeremyevans0 (Jeremy Evans). Backport deleted (2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN) Status changed from Open to Assigned Tracker changed from Bug to Feature This makes sense to me. However, there is a explicit test currently that array arguments are not accepted. So this must be considered a feature request and not a bug. I've submitted an upstream pull request that implements this feature: https://github.com/ruby/set/pull/18 ---------------------------------------- Feature #17838: `Set#intersect?` and enumerables https://bugs.ruby-lang.org/issues/17838#change-92503 * Author: marcandre (Marc-Andre Lafortune) * Status: Assigned * Priority: Normal * Assignee: knu (Akinori MUSHA) ---------------------------------------- `Set#intersect?` currently accepts only a `set` argument. It should accept an enumerable argument: ```ruby [1, 2, 3].intersect?(Set[2, 3, 4]) # => true Set[2, 3, 4].intersection([1, 2, 3]) # => Set[2, 3] Set[2, 3, 4].intersect?([1, 2, 3]) # => ArgumentError ``` I expect `set.intersect?(arg)` to be an optimized version of `!set.intersection(arg).empty?` Should I prepare a PR? -- 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>