From: sawadatsuyoshi@...
Date: 2020-08-25T23:37:07+00:00
Subject: [ruby-core:99692] [Ruby master Bug#17030] Enumerable#grep{_v} should be optimized for Regexp

Issue #17030 has been updated by sawa (Tsuyoshi Sawada).


I feel scivola20 (sciv ola)'s idea promising, but have a feeling that it is going to introduce the same kind of mess as when `"string"f` notation was introduced. People are going to need to write `/regex/f` all over the place.

Just by analogy from the situation with strings, what about introducing the following pragma, which will make all regex literals on that page fast regex literals (i.e., `===` becomes `match?`)?

```ruby
# boolean_regex_literal: true
```

And perhaps in the long run, Matz might want to make all regex literals work like that.

----------------------------------------
Bug #17030: Enumerable#grep{_v} should be optimized for Regexp
https://bugs.ruby-lang.org/issues/17030#change-87183

* Author: marcandre (Marc-Andre Lafortune)
* Status: Open
* Priority: Normal
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
Currently:

```ruby
array.select { |e| e.match?(REGEXP) }

# about 3x faster and 6x more memory efficient than
array.grep(REGEXP)
```

This is because `grep` calls `Regexp#===` which creates useless `MatchData`



-- 
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>