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

do statement is not fully considered to be a loop #6475

Open
p6rt opened this issue Sep 4, 2017 · 3 comments
Open

do statement is not fully considered to be a loop #6475

p6rt opened this issue Sep 4, 2017 · 3 comments
Labels

Comments

@p6rt
Copy link

p6rt commented Sep 4, 2017

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

Searchable as RT132025$

@p6rt
Copy link
Author

p6rt commented Sep 4, 2017

From @skids

Please combine RT#​124573, RT#​124274, RT#​124275, and RT#​124276 into this ticket.

The tests referenced in those auto-generated tickets all currently fail due to
the fact that "do" statements are not fully considered to be loops by rakudo's
in-loop control statements.

That it should be a loop is in S04/"The do-once loop."

In the case of RT#​124274 the initial failure mode has since changed. Originally
it had problems with the label, but since then the failure is now an X​::ControlFlow
as in cases without the label.

@p6rt
Copy link
Author

p6rt commented Sep 4, 2017

From @AlexDaniel

Thanks. Done.

Unfortunately, RT does not save titles of merged tickets, so I think we lost a little bit of information after the merge. But fear not, these ticket IDs are referenced in S04-statements/do.t, so once this ticket is resolved please also unskip the tests.

On 2017-09-03 19​:01​:48, bri@​abrij.org wrote​:

Please combine RT#​124573, RT#​124274, RT#​124275, and RT#​124276 into
this ticket.

The tests referenced in those auto-generated tickets all currently
fail due to
the fact that "do" statements are not fully considered to be loops by
rakudo's
in-loop control statements.

That it should be a loop is in S04/"The do-once loop."

In the case of RT#​124274 the initial failure mode has since changed.
Originally
it had problems with the label, but since then the failure is now an
X​::ControlFlow
as in cases without the label.

@p6rt
Copy link
Author

p6rt commented Sep 4, 2017

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

@p6rt p6rt added the Bug label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant