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

Expressions involving two sequence operators time out or give a spurious error in Rakudo #2466

Closed
p6rt opened this issue Sep 9, 2011 · 4 comments
Labels

Comments

@p6rt
Copy link

p6rt commented Sep 9, 2011

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

Searchable as RT98790$

@p6rt
Copy link
Author

p6rt commented Sep 9, 2011

From @masak

<masak> niecza​: .say for (1 ... 10) Z (10 ... 1)
<p6eval> niecza v9-11-g0f286c3​:
OUTPUT«1␤10␤2␤9␤3␤8␤4␤7␤5␤6␤6␤5␤7␤4␤8␤3␤9␤2␤10␤1␤»
<masak> rakudo​: .say for (1 ... 10) Z (10 ... 1)
<p6eval> rakudo f9d94f​: OUTPUT«(timeout)»
* masak submits rakudobug
<masak> niecza​: .say for (1 ... 10), (10 ... 1)
<p6eval> niecza v9-11-g0f286c3​:
OUTPUT«1␤2␤3␤4␤5␤6␤7␤8␤9␤10␤10␤9␤8␤7␤6␤5␤4␤3␤2␤1␤»
<masak> rakudo​: .say for (1 ... 10), (10 ... 1)
<p6eval> rakudo f9d94f​: OUTPUT«Not enough positional parameters
passed; got 0 but expected 1 [...]

Niecza is right in both cases. Rakudo times out or gives an incorrect
error; both of these behaviors are wrong.

@p6rt
Copy link
Author

p6rt commented Sep 9, 2011

From @pmichaud

Now fixed in f9d94fe. There were already todo'd tests for this bug in
spectests, they're now un-todo'd and marked with this ticket number.

Thanks for the report, closing ticket!

Pm

1 similar comment
@p6rt
Copy link
Author

p6rt commented Sep 9, 2011

From @pmichaud

Now fixed in f9d94fe. There were already todo'd tests for this bug in
spectests, they're now un-todo'd and marked with this ticket number.

Thanks for the report, closing ticket!

Pm

@p6rt
Copy link
Author

p6rt commented Sep 9, 2011

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

@p6rt p6rt closed this as completed Sep 9, 2011
@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