Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strange error when attempting to redo a supply block #5482

Open
p6rt opened this issue Jul 24, 2016 · 7 comments
Open

Strange error when attempting to redo a supply block #5482

p6rt opened this issue Jul 24, 2016 · 7 comments
Labels

Comments

@p6rt
Copy link

@p6rt p6rt commented Jul 24, 2016

Migrated from rt.perl.org#128718 (status was 'open')

Searchable as RT128718$

@p6rt

This comment has been minimized.

Copy link
Author

@p6rt p6rt commented Jul 24, 2016

From @zoffixznet

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

@p6rt

This comment has been minimized.

Copy link
Author

@p6rt p6rt commented Aug 25, 2016

From @coke

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

--
Will "Coke" Coleda

@p6rt

This comment has been minimized.

Copy link
Author

@p6rt p6rt commented Aug 25, 2016

The RT System itself - Status changed from 'new' to 'open'

@p6rt

This comment has been minimized.

Copy link
Author

@p6rt p6rt commented Jul 9, 2017

From @dogbert17

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.

@p6rt

This comment has been minimized.

Copy link
Author

@p6rt p6rt commented Jul 9, 2017

@dogbert17 - Status changed from 'open' to 'rejected'

@p6rt

This comment has been minimized.

Copy link
Author

@p6rt p6rt commented Jul 10, 2017

From @AlexDaniel

Since when are we rejecting tickets like that? :)

The title says “Strange error”. Current error message is​:
===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​:

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.

@p6rt

This comment has been minimized.

Copy link
Author

@p6rt p6rt commented Jul 10, 2017

@AlexDaniel - Status changed from 'rejected' to 'open'

@p6rt p6rt added the conc label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.