ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: mame@ruby-lang.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:91068] [Ruby trunk Feature#15523] `Range#begin` and `Range#end`
Date: Sun, 13 Jan 2019 13:17:41 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-76290.20190113131739.8d12fb51f1fee215@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15523.20190111044448@ruby-lang.org

Issue #15523 has been updated by mame (Yusuke Endoh).


Objection.

I understand that "your problem" is confusion between a keyword "begin" and "Range#keyword".  First, I have never been confused by the fact.  Then,

> * Let Range#begin and Range#end be aliases of Range#first and Range#last, respectively, or

This does not solve your problem at all.

> * Let Range#begin and Range#end be obsolete after a migration path of waning against their use and recommending the use of Range#first and Range#last instead.

Your problem looks too weak to me to deprecate an existing feature.


Off-topic: Could you please make the title informative?  "`Range#begin` and `Range#end`" doesn't tell me what is a problem or proposal.  I never say this to a newbie, but you have already opened hundreds of tickets.

----------------------------------------
Feature #15523: `Range#begin` and `Range#end`
https://bugs.ruby-lang.org/issues/15523#change-76290

* Author: sawa (Tsuyoshi Sawada)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
----------------------------------------
My understanding is that `Range#begin` and `Range#end`'s features are just subsets of `Range#first` and `Range#last`, respectively. And since they are slightly confusing with the keywords `begin` and `end`, I propose to either:

* Let `Range#begin` and `Range#end` be aliases of `Range#first` and `Range#last`, respectively, or
* Let `Range#begin` and `Range#end` be obsolete after a migration path of waning against their use and recommending the use of `Range#first` and `Range#last` instead.





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

  parent reply	other threads:[~2019-01-13 13:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-15523.20190111044448@ruby-lang.org>
2019-01-11  4:44 ` [ruby-core:91010] [Ruby trunk Bug#15523] `Range#begin` and `Range#end` sawadatsuyoshi
2019-01-11  4:45 ` [ruby-core:91011] " sawadatsuyoshi
2019-01-11  4:51 ` [ruby-core:91012] [Ruby trunk Feature#15523] " kou
2019-01-11 11:13 ` [ruby-core:91020] " shevegen
2019-01-13 13:17 ` mame [this message]
2019-01-14 12:52 ` [ruby-core:91080] " muraken
2019-01-14 14:15 ` [ruby-core:91081] " muraken
2019-01-15  3:53 ` [ruby-core:91093] [Ruby trunk Feature#15523] Let `Range#begin` and `Range#end` be aliases of Range#first and Range#last sawadatsuyoshi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-76290.20190113131739.8d12fb51f1fee215@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).