Skip Menu |
Report information
Id: 128718
Status: open
Priority: 0/
Queue: perl6

Owner: Nobody
Requestors: cpan [at] zoffix.com
Cc:
AdminCc:

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



Subject: Strange error when attempting to redo a supply block
Download (untitled) / with headers
text/plain 274b
Not even sure what causes that, but removing the `redo` avoids the error. $ perl6 -e 'react { whenever supply { emit 42; redo } { .say } }' 42 No such method 'CALL-ME' for invocant of type 'Bool' in block <unit> at -e line 1 -- Cheers, ZZ | https://twitter.com/zoffix
RT-Send-CC: perl6-compiler [...] perl.org
Download (untitled) / with headers
text/plain 608b
On Sat Jul 23 20:47:04 2016, cpan@zoffix.com wrote: Show quoted text
> Not even sure what causes that, but removing the `redo` avoids the error. > > $ perl6 -e 'react { whenever supply { emit 42; redo } { .say } }' > 42 > No such method 'CALL-ME' for invocant of type 'Bool' > in block <unit> at -e line 1 > >
Behavior has changed: $ perl6 -e 'react { whenever supply { emit 42; redo } { .say } }' 42 Access denied to keep/break this Promise; already vowed in any at /Users/coke/.rakudobrew/moar-2016.08.1/install/share/perl6/runtime/CORE.setting.moarvm line 1 in block <unit> at -e line 1 -- Will "Coke" Coleda
On Thu, 25 Aug 2016 07:14:03 -0700, coke wrote: Show quoted text
> On Sat Jul 23 20:47:04 2016, cpan@zoffix.com wrote:
> > Not even sure what causes that, but removing the `redo` avoids the > > error. > > > > $ perl6 -e 'react { whenever supply { emit 42; redo } { .say } }' > > 42 > > No such method 'CALL-ME' for invocant of type 'Bool' > > in block <unit> at -e line 1 > > > >
> > Behavior has changed: > > $ perl6 -e 'react { whenever supply { emit 42; redo } { .say } }' > 42 > Access denied to keep/break this Promise; already vowed > in any at /Users/coke/.rakudobrew/moar- > 2016.08.1/install/share/perl6/runtime/CORE.setting.moarvm line 1 > in block <unit> at -e line 1
Running it with a recent version gives the following result dogbert@dogbert-VirtualBox ~ $ perl6 -e 'react { whenever supply { emit 42; redo } { .say } }' 42 ===SORRY!=== redo without loop construct If this message is correct then the original code snippet should never have worked in the first place. Rejecting issue. Reopen if you think this is a mistake.
Since when are we rejecting tickets like that? :)

The title says “Strange error”. Current error message is:
Show quoted text
===SORRY!===
redo without loop construct

Two things:
1) No line number
2) Even if the line number was there, we don't want the behavior of this to be changing like crazy. See output on all releases: https://gist.github.com/Whateverable/e6e0d116d73ef3b467b55a779ee657cd . The fact that it was changing like this means that it may be a good idea to add a test (for the error message), even if the original code is not supposed to work.

I'm not against repurposing this ticket as [LTA], but rejecting? I don't think it's a good idea…

On 2017-07-09 16:16:51, jan-olof.hendig@bredband.net wrote:
Show quoted text
> On Thu, 25 Aug 2016 07:14:03 -0700, coke wrote:
> > On Sat Jul 23 20:47:04 2016, cpan@zoffix.com wrote:
> > > Not even sure what causes that, but removing the `redo` avoids the
> > > error.
> > >
> > > $ perl6 -e 'react { whenever supply { emit 42; redo } { .say } }'
> > > 42
> > > No such method 'CALL-ME' for invocant of type 'Bool'
> > > in block <unit> at -e line 1
> > >
> > >
> >
> > Behavior has changed:
> >
> > $ perl6 -e 'react { whenever supply { emit 42; redo } { .say } }'
> > 42
> > Access denied to keep/break this Promise; already vowed
> > in any at /Users/coke/.rakudobrew/moar-
> > 2016.08.1/install/share/perl6/runtime/CORE.setting.moarvm line 1
> > in block <unit> at -e line 1
>
> Running it with a recent version gives the following result
>
> dogbert@dogbert-VirtualBox ~ $ perl6 -e 'react { whenever supply {
> emit 42; redo } { .say } }'
> 42
> ===SORRY!===
> redo without loop construct
>
> If this message is correct then the original code snippet should never
> have worked in the first place.
> Rejecting issue. Reopen if you think this is a mistake.




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