[#114774] [Ruby master Feature#19884] Make Safe Navigation Operator work on classes — "p8 (Petrik de Heus) via ruby-core" <ruby-core@...>
Issue #19884 has been reported by p8 (Petrik de Heus).
13 messages
2023/09/15
[ruby-core:114610] [Ruby master Bug#19859] Start & Finish, Begin & End
From:
"thoran (thoran not blank) via ruby-core" <ruby-core@...>
Date:
2023-09-01 02:19:19 UTC
List:
ruby-core #114610
Issue #19859 has been reported by thoran (thoran not blank). ---------------------------------------- Bug #19859: Start & Finish, Begin & End https://bugs.ruby-lang.org/issues/19859 * Author: thoran (thoran not blank) * Status: Open * Priority: Normal * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- In English "start" is paired with "finish" and "begin" is paired with "end". While "start" and "begin", and "finish" and "end" have similar meanings they are not the same. Hence it should be: String#begin_with? & String#end_with? or maybe String#start_with? & String#finish_with? or both; but not certainly not String#start_with? & String#end_with? as it is presently. Further, I would argue that it should be only String#begin_with? & String#end_with? because "start" and "finish" imply temporality and strings don't have that connotation. Hence the solution here for me would be to: /String#start_with?/String#begin_with?/. If however there is a desire to retain interface compatibility and to adhere to TMTOWTDI, then introduce both: String#begin_with? and String#finish_with? -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/