Skip Menu |
Report information
Id: 131018
Status: resolved
Priority: 0/
Queue: perl6

Owner: Nobody
Requestors: alex.jakimenko [at] gmail.com
Cc:
AdminCc:

Severity: (no value)
Tag: testneeded
Platform: (no value)
Patch Status: (no value)
VM: (no value)



Subject: [REGRESSION] Some rotor cases are no longer working as expected (.rotor: 2 => -2, 1)
Download (untitled) / with headers
text/plain 816b
Code: .say for <a b c d e f>.rotor(2 => -2, 1) Result (2015.12..2016.12): (a b) (a) (b c) (b) (c d) (c) (d e) (d) (e f) (e) Result (2017.01): Rotorizing gap is out of range. Is: -2, should be in -1..^Inf; Ensure a negative gap is not larger than the length of the sublist in block <unit> at /tmp/uYWEuzId1z line 1 Result (2017.02,2017.03,HEAD(fbe7ace)): (a b) The first change happened in https://github.com/rakudo/rakudo/commit/d7b82149d31da04763f0d269f0e3e76f67efd5fe Then it was brought back to life in https://github.com/rakudo/rakudo/commit/b9d9279a6d2aff68791b8085d8e09678886026bb Previous behavior (2015.12-ish) is what I expect to happen. It is consistent with behavior observed in other cases, for example: Code: .say for <a b c d e f>.rotor(2 => -1, 1) Result: (a b) (b) (c d) (d) (e f) (f)
Date: Mon, 20 Mar 2017 00:24:01 +0100
Subject: Re: [perl #131018] [REGRESSION] Some rotor cases are no longer working as expected (.rotor: 2 => -2, 1)
From: Elizabeth Mattijsen <liz [...] dijkmat.nl>
To: "Aleks-Daniel Jakimenko-Aleksejev (via RT)" <perl6-bugs-followup [...] perl.org>
Download (untitled) / with headers
text/plain 1.2k
am looking at it Show quoted text
> On 19 Mar 2017, at 22:03, Aleks-Daniel Jakimenko-Aleksejev (via RT) <perl6-bugs-followup@perl.org> wrote: > > # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev > # Please include the string: [perl #131018] > # in the subject line of all future correspondence about this issue. > # <URL: https://rt.perl.org/Ticket/Display.html?id=131018 > > > > Code: > .say for <a b c d e f>.rotor(2 => -2, 1) > > > Result (2015.12..2016.12): > (a b) > (a) > (b c) > (b) > (c d) > (c) > (d e) > (d) > (e f) > (e) > > > Result (2017.01): > Rotorizing gap is out of range. Is: -2, should be in -1..^Inf; > Ensure a negative gap is not larger than the length of the sublist > in block <unit> at /tmp/uYWEuzId1z line 1 > > > Result (2017.02,2017.03,HEAD(fbe7ace)): > (a b) > > > > The first change happened in https://github.com/rakudo/rakudo/commit/d7b82149d31da04763f0d269f0e3e76f67efd5fe > Then it was brought back to life in https://github.com/rakudo/rakudo/commit/b9d9279a6d2aff68791b8085d8e09678886026bb > > Previous behavior (2015.12-ish) is what I expect to happen. It is consistent with behavior observed in other cases, for example: > > Code: > .say for <a b c d e f>.rotor(2 => -1, 1) > > Result: > (a b) > (b) > (c d) > (d) > (e f) > (f)
To: "Aleks-Daniel Jakimenko-Aleksejev (via RT)" <perl6-bugs-followup [...] perl.org>
Subject: Re: [perl #131018] [REGRESSION] Some rotor cases are no longer working as expected (.rotor: 2 => -2, 1)
From: Elizabeth Mattijsen <liz [...] dijkmat.nl>
Date: Mon, 20 Mar 2017 12:45:08 +0100
Download (untitled) / with headers
text/plain 1.3k
Fixed with https://github.com/rakudo/rakudo/commit/5917b817c6 , tests needed Show quoted text
> On 19 Mar 2017, at 22:03, Aleks-Daniel Jakimenko-Aleksejev (via RT) <perl6-bugs-followup@perl.org> wrote: > > # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev > # Please include the string: [perl #131018] > # in the subject line of all future correspondence about this issue. > # <URL: https://rt.perl.org/Ticket/Display.html?id=131018 > > > > Code: > .say for <a b c d e f>.rotor(2 => -2, 1) > > > Result (2015.12..2016.12): > (a b) > (a) > (b c) > (b) > (c d) > (c) > (d e) > (d) > (e f) > (e) > > > Result (2017.01): > Rotorizing gap is out of range. Is: -2, should be in -1..^Inf; > Ensure a negative gap is not larger than the length of the sublist > in block <unit> at /tmp/uYWEuzId1z line 1 > > > Result (2017.02,2017.03,HEAD(fbe7ace)): > (a b) > > > > The first change happened in https://github.com/rakudo/rakudo/commit/d7b82149d31da04763f0d269f0e3e76f67efd5fe > Then it was brought back to life in https://github.com/rakudo/rakudo/commit/b9d9279a6d2aff68791b8085d8e09678886026bb > > Previous behavior (2015.12-ish) is what I expect to happen. It is consistent with behavior observed in other cases, for example: > > Code: > .say for <a b c d e f>.rotor(2 => -1, 1) > > Result: > (a b) > (b) > (c d) > (d) > (e f) > (f)
Download (untitled) / with headers
text/plain 1.5k
On Mon, 20 Mar 2017 04:46:18 -0700, elizabeth wrote: Show quoted text
> Fixed with https://github.com/rakudo/rakudo/commit/5917b817c6 , tests > needed >
> > On 19 Mar 2017, at 22:03, Aleks-Daniel Jakimenko-Aleksejev (via RT) > > <perl6-bugs-followup@perl.org> wrote: > > > > # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev > > # Please include the string: [perl #131018] > > # in the subject line of all future correspondence about this issue. > > # <URL: https://rt.perl.org/Ticket/Display.html?id=131018 > > > > > > > Code: > > .say for <a b c d e f>.rotor(2 => -2, 1) > > > > > > Result (2015.12..2016.12): > > (a b) > > (a) > > (b c) > > (b) > > (c d) > > (c) > > (d e) > > (d) > > (e f) > > (e) > > > > > > Result (2017.01): > > Rotorizing gap is out of range. Is: -2, should be in -1..^Inf; > > Ensure a negative gap is not larger than the length of the sublist > > in block <unit> at /tmp/uYWEuzId1z line 1 > > > > > > Result (2017.02,2017.03,HEAD(fbe7ace)): > > (a b) > > > > > > > > The first change happened in > > https://github.com/rakudo/rakudo/commit/d7b82149d31da04763f0d269f0e3e76f67efd5fe > > Then it was brought back to life in > > https://github.com/rakudo/rakudo/commit/b9d9279a6d2aff68791b8085d8e09678886026bb > > > > Previous behavior (2015.12-ish) is what I expect to happen. It is > > consistent with behavior observed in other cases, for example: > > > > Code: > > .say for <a b c d e f>.rotor(2 => -1, 1) > > > > Result: > > (a b) > > (b) > > (c d) > > (d) > > (e f) > > (f)
Tests added: https://github.com/perl6/roast/pull/287


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

For issues related to this RT instance (aka "perlbug"), please contact perlbug-admin at perl.org