From: duerst@...
Date: 2019-11-18T03:42:24+00:00
Subject: [ruby-dev:50866] [Ruby master Feature#16348] Proposal: Symbol#start_with?, Symbol#end_with?, and Symbol#include?

Issue #16348 has been updated by duerst (Martin Dürst).


I personally think that we should be restrictive in adding new methods to `Symbol`. Otherwise, this very quickly becomes a slippery slope, and the distinction between `Symbol` and `String` becomes less and less clear.

I was personally surprised when I implemented feature #10085 that `Symbol` had `#upcase` and friends, I wouldn't have guessed that. 

----------------------------------------
Feature #16348: Proposal: Symbol#start_with?, Symbol#end_with?, and Symbol#include?
https://bugs.ruby-lang.org/issues/16348#change-82710

* Author: kamipo (Ryuta Kamizono)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
----------------------------------------
When replacing #match? to #start_with?, #end_with?, and #include? for some reason (address to https://bugs.ruby-lang.org/issues/13083 etc), we frequently hit missing Symbol#start_with?, Symbol#end_with?, and Symbol#include? in spite of Symbol#match? exists.

https://github.com/rails/rails/commit/63256bc5d7dd77b2cce82df46c53249dab2dc2a8
https://github.com/rails/rails/commit/a8e812964d711fa03843e76ae50f5ff81cdc9e00

Is this inconsistency intentional?
If not so, Symbol#start_with?, Symbol#end_with?, and Symbol#include? prevents such like an issue.



-- 
https://bugs.ruby-lang.org/