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

redo without a loop no longer prints the line number, also claims it is a compile-time error (redo) #5940

Closed
p6rt opened this issue Dec 29, 2016 · 4 comments
Labels

Comments

@p6rt
Copy link

@p6rt p6rt commented Dec 29, 2016

Migrated from rt.perl.org#130442 (status was 'resolved')

Searchable as RT130442$

@p6rt
Copy link
Author

@p6rt p6rt commented Dec 29, 2016

From @AlexDaniel

Code​:
say 42; redo

Result (2015.12,2016.05)​:
42
redo without loop construct
  in block <unit> at /tmp/rQ_1K_fvaD line 1

Result (2016.06,HEAD)​:
42
===SORRY!===
redo without loop construct

It should print the line number and it should not say “===SORRY!===” because it is not a compile-time error.

Bisectable gives a list of commits that could have caused this​:
e609822f01b82608b1b1c869032c95e9641172ce
615d30c39eba318f7449b94bbbd0295e2fd75387
8beb87b415014254412409d56378afb3ed5f14d9
05170e0c14969663c816ee1c5aaa019d70938247
899e0fd4c1ce51bc492666ffc69627c502f657f7
e5443765d4bce0697c6191dd2b17db3044e027ab
fcd0093b43614ce91caeb8c23e2bbcff68d54f72
04929feeb06fa851d77ef5efa6be35248301f88c
7ee6578ce99aae069349c283012ae7e45dfd75ec
519e76487ddd1546b319bfbd47661beac2417d61

@p6rt
Copy link
Author

@p6rt p6rt commented Dec 29, 2016

From @AlexDaniel

Of course, same thing with “next” and “last” (is there anything else?)

On 2016-12-29 09​:13​:24, alex.jakimenko@​gmail.com wrote​:

Code​:
say 42; redo

Result (2015.12,2016.05)​:
42
redo without loop construct
in block <unit> at /tmp/rQ_1K_fvaD line 1

Result (2016.06,HEAD)​:
42
===SORRY!===
redo without loop construct

It should print the line number and it should not say “===SORRY!===”
because it is not a compile-time error.

Bisectable gives a list of commits that could have caused this​:
e609822f01b82608b1b1c869032c95e9641172ce
615d30c39eba318f7449b94bbbd0295e2fd75387
8beb87b415014254412409d56378afb3ed5f14d9
05170e0c14969663c816ee1c5aaa019d70938247
899e0fd4c1ce51bc492666ffc69627c502f657f7
e5443765d4bce0697c6191dd2b17db3044e027ab
fcd0093b43614ce91caeb8c23e2bbcff68d54f72
04929feeb06fa851d77ef5efa6be35248301f88c
7ee6578ce99aae069349c283012ae7e45dfd75ec
519e76487ddd1546b319bfbd47661beac2417d61

@p6rt
Copy link
Author

@p6rt p6rt commented Mar 1, 2019

From @AlexDaniel

Moved to rakudo/rakudo#2725

On 2016-12-29 14​:43​:03, alex.jakimenko@​gmail.com wrote​:

Of course, same thing with “next” and “last” (is there anything else?)

On 2016-12-29 09​:13​:24, alex.jakimenko@​gmail.com wrote​:

Code​:
say 42; redo

Result (2015.12,2016.05)​:
42
redo without loop construct
in block <unit> at /tmp/rQ_1K_fvaD line 1

Result (2016.06,HEAD)​:
42
===SORRY!===
redo without loop construct

It should print the line number and it should not say “===SORRY!===”
because it is not a compile-time error.

Bisectable gives a list of commits that could have caused this​:
e609822f01b82608b1b1c869032c95e9641172ce
615d30c39eba318f7449b94bbbd0295e2fd75387
8beb87b415014254412409d56378afb3ed5f14d9
05170e0c14969663c816ee1c5aaa019d70938247
899e0fd4c1ce51bc492666ffc69627c502f657f7
e5443765d4bce0697c6191dd2b17db3044e027ab
fcd0093b43614ce91caeb8c23e2bbcff68d54f72
04929feeb06fa851d77ef5efa6be35248301f88c
7ee6578ce99aae069349c283012ae7e45dfd75ec
519e76487ddd1546b319bfbd47661beac2417d61

@p6rt
Copy link
Author

@p6rt p6rt commented Mar 1, 2019

@AlexDaniel - Status changed from 'new' to 'resolved'

@p6rt p6rt closed this Mar 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.