ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: mail@stefanschuessler.de
To: ruby-core@ruby-lang.org
Subject: [ruby-core:81750] [Ruby trunk Bug#13663] `String#upto` doesn't work as expected
Date: Fri, 23 Jun 2017 11:47:13 +0000	[thread overview]
Message-ID: <redmine.journal-65450.20170623114713.8493d39a8a5c4275@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-13663.20170615072454@ruby-lang.org

Issue #13663 has been updated by sos4nt (Stefan Schüßler).


I'm not asking for consistency between `String#succ` and `String#<=>` (although that would be desirable). I do understand that the discrepancy may result in surprising results when generating sequences via `Range` because `Range` relies on these methods. `Range` checks via `<=>` if the value generated by `succ` is indeed a successor.

But `String#upto` doesn't have the limitations `Range` has. It doesn't have to work with arbitrary objects and it doesn't have to depend on `<=>`. It can apply whatever logic is needed to ensure a sane result.

----------------------------------------
Bug #13663: `String#upto` doesn't work as expected
https://bugs.ruby-lang.org/issues/13663#change-65450

* Author: sos4nt (Stefan Schüßler)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin15]
* Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN
----------------------------------------
Given that `String#upto` uses `String#succ` to generate successive values, I'd expect

```ruby
'x'.upto('ac').to_a #=> []
```

to return:

```ruby
["x", "y", "z", "aa", "ab", "ac"]
```

Instead, an empty array is returned.

This seems to depend on whether the the receiver is greater than the argument or not:

```ruby
'x' <=> 'ac' #=> 1
```

It works just fine in this case:

```ruby
'b'.upto('ca').to_a
#=> ["b", "c", "d", "e", "f", "g", "h", "i", "j", "k", "l", "m", "n",
#    "o", "p", "q", "r", "s", "t", "u", "v", "w", "x", "y", "z", "aa",
#    "ab", "ac", "ad", "ae", "af", "ag", "ah", "ai", "aj", "ak", "al",
#    "am", "an", "ao", "ap", "aq", "ar", "as", "at", "au", "av", "aw",
#    "ax", "ay", "az", "ba", "bb", "bc", "bd", "be", "bf", "bg", "bh",
#    "bi", "bj", "bk", "bl", "bm", "bn", "bo", "bp", "bq", "br", "bs",
#    "bt", "bu", "bv", "bw", "bx", "by", "bz", "ca"]
```

Presumably because of:

```ruby
'b' <=> 'ca' #=> -1
```




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

      parent reply	other threads:[~2017-06-23 11:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-13663.20170615072454@ruby-lang.org>
2017-06-15  7:24 ` [ruby-core:81690] [Ruby trunk Bug#13663] `String#upto` doesn't work as expected mail
2017-06-15 12:53 ` [ruby-core:81691] " zverok.offline
2017-06-15 13:08 ` [ruby-core:81692] " hanmac
2017-06-23 11:47 ` mail [this message]

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-65450.20170623114713.8493d39a8a5c4275@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).