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

'Rakudo still uses Nil here' (Or bogus test?) #3883

Closed
p6rt opened this issue May 3, 2015 · 7 comments
Closed

'Rakudo still uses Nil here' (Or bogus test?) #3883

p6rt opened this issue May 3, 2015 · 7 comments

Comments

@p6rt
Copy link

p6rt commented May 3, 2015

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

Searchable as RT124568$

@p6rt
Copy link
Author

p6rt commented Sep 24, 2015

From @coke

Pretty sure this predates the GLR - the current behavior is that the list has no holes, whereas we used to expect a Nil or a ().

This ticket can probably be closed (and the tests removed) with review.

--
Will "Coke" Coleda

@p6rt
Copy link
Author

p6rt commented Sep 24, 2015

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

@p6rt
Copy link
Author

p6rt commented May 20, 2016

From @smls

Yeah, the test seems bogus.

I'll abuse the `testneeded` tag to make sure this ticket can be found by the Roast experts... :)

@p6rt
Copy link
Author

p6rt commented Jul 7, 2016

From @zoffixznet

Since the topic of this ticket is hidden in the changed title message, to clarify, it's about this test and whether it should be removed now​: https://github.com/perl6/roast/blob/ab74762da156fa6fda5dd39281f7ffcc361d5a88/S04-statements/for.t#L473

@p6rt
Copy link
Author

p6rt commented Aug 14, 2016

From @TimToady

Test was bogus. Replaced with test that assumes Empty semantics on next.

test fixed in 06f9c5d010986a7a8dde907971e25985e8ba4601

1 similar comment
@p6rt
Copy link
Author

p6rt commented Aug 14, 2016

From @TimToady

Test was bogus. Replaced with test that assumes Empty semantics on next.

test fixed in 06f9c5d010986a7a8dde907971e25985e8ba4601

@p6rt
Copy link
Author

p6rt commented Aug 14, 2016

@TimToady - Status changed from 'open' to 'resolved'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant