From: justcolin@... Date: 2016-12-21T19:17:58+00:00 Subject: [ruby-core:78793] [Ruby trunk Feature#13048] Better way to do Regexp.new(Regexp.escape("some string")) Issue #13048 has been updated by Colin Fulton. It would be nice to have a real/more-idiomatic way instead of a hack, and that hack doesn't support duck typing, while adding `#to_regexp` to `String` does. ---------------------------------------- Feature #13048: Better way to do Regexp.new(Regexp.escape("some string")) https://bugs.ruby-lang.org/issues/13048#change-62201 * Author: Colin Fulton * Status: Open * Priority: Normal * Assignee: * Target version: ---------------------------------------- It is relatively common to call `Regexp.new(Regexp.escape("some string"))` or `Regexp.new(Regexp.quote("some string"))` in Ruby (a quick search turns up over half a million matches in Github). However, these seems rather cumbersome. It would be nice to have a class instance method on `Regexp` and/or an instance method on `String` to go directly to an escaped regular expression. Personally I'd rather see `#to_regexp` added to `String`. This would not overlap with the functionality that `Rexexp.new("string")` provides since that doesn't quote the `String`. It would also be good to see [9846](https://bugs.ruby-lang.org/issues/9846) addressed along with this request so one could more easily duck type a method to accept both `Regexp` and `String` arguments. Thoughts? -- https://bugs.ruby-lang.org/ Unsubscribe: