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

[|] 1..5 should give a flat any(1..5) junction, not nested junctions in Rakudo #2741

Closed
p6rt opened this issue Apr 30, 2012 · 7 comments
Closed

Comments

@p6rt
Copy link

p6rt commented Apr 30, 2012

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

Searchable as RT112696$

@p6rt
Copy link
Author

p6rt commented Apr 30, 2012

From @masak

<TimToady> perl6​: say ([|] 1..5).perl
<p6eval> niecza v16-23-gaa61ed5​: OUTPUT«any(1, 2, 3, 4, 5)␤»
<p6eval> ..pugs​: OUTPUT«(1 | 2 | 3 | 4 | 5)␤»
<p6eval> ..rakudo 110f35​: OUTPUT«any(any(any(any(1, 2), 3), 4), 5)␤»
<TimToady> rakudobug
* masak submits any(any(any(any(1, 2), 3), 4), 5) rakudobug

@p6rt
Copy link
Author

p6rt commented May 4, 2012

From @pmichaud

Now fixed in 7eae9b2​:

  pmichaud@​kiwi​:~/p6/rakudo$ ./perl6
  > say ([|] 1..5).perl
  any(1, 2, 3, 4, 5)

Ticket can be closed with appropriate spectests.

Pm

@p6rt
Copy link
Author

p6rt commented May 4, 2012

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

@p6rt
Copy link
Author

p6rt commented May 4, 2012

From @moritz

I'm curious, is there any semantic difference between the nested
junctions and a flat one? I'd need that for testing. If there is none,
I'd close without any tests.

@p6rt
Copy link
Author

p6rt commented May 4, 2012

From @masak

On Fri, May 4, 2012 at 8​:09 AM, Moritz Lenz via RT
<perl6-bugs-followup@​perl.org> wrote​:

I'm curious, is there any semantic difference between the nested
junctions and a flat one? I'd need that for testing. If there is none,
I'd close without any tests.

The only semantic difference I can think of has to do with .eigenvalues

@p6rt
Copy link
Author

p6rt commented Jun 27, 2012

From @moritz

Closing without test, because I can't think of any sensible, robust test
for it.

@p6rt
Copy link
Author

p6rt commented Jun 27, 2012

@moritz - 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