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

expected Positional but got Seq #4691

Closed
p6rt opened this issue Oct 29, 2015 · 8 comments
Closed

expected Positional but got Seq #4691

p6rt opened this issue Oct 29, 2015 · 8 comments
Labels
glr JVM Related to Rakudo-JVM

Comments

@p6rt
Copy link

p6rt commented Oct 29, 2015

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

Searchable as RT126493$

@p6rt
Copy link
Author

p6rt commented Oct 29, 2015

From @coke

Several tests in t/spec/S32-list/produce.t fail only on the JVM with
this error message.

--
Will "Coke" Coleda

@p6rt
Copy link
Author

p6rt commented Nov 18, 2015

From @usev6

I fudged some more tests with this error mode in S32-list/squish.t

The error happens in /src/core/Mu.pm when binding to @​a in the signature of this sub definition​:

multi sub infix​:<eqv>(@​a, @​b) {
...
}

Moar and JVM behave differently when trying to bind a Seq in such a case​:

$ perl6-m -e 'sub foo (@​a) { say @​a.WHAT }; my $a = Seq.new((1..2).iterator); foo($a)'
(List)

$ perl6-j -e 'sub foo (@​a) { say @​a.WHAT }; my $a = Seq.new((1..2).iterator); foo($a)'
Type check failed in binding @​a; expected Positional but got Seq
  in sub foo at -e​:1
  in block <unit> at -e​:1

1 similar comment
@p6rt
Copy link
Author

p6rt commented Nov 18, 2015

From @usev6

I fudged some more tests with this error mode in S32-list/squish.t

The error happens in /src/core/Mu.pm when binding to @​a in the signature of this sub definition​:

multi sub infix​:<eqv>(@​a, @​b) {
...
}

Moar and JVM behave differently when trying to bind a Seq in such a case​:

$ perl6-m -e 'sub foo (@​a) { say @​a.WHAT }; my $a = Seq.new((1..2).iterator); foo($a)'
(List)

$ perl6-j -e 'sub foo (@​a) { say @​a.WHAT }; my $a = Seq.new((1..2).iterator); foo($a)'
Type check failed in binding @​a; expected Positional but got Seq
  in sub foo at -e​:1
  in block <unit> at -e​:1

@p6rt
Copy link
Author

p6rt commented Nov 18, 2015

@usev6 - Status changed from 'new' to 'open'

@p6rt
Copy link
Author

p6rt commented Nov 21, 2015

From @peschwa

On Wed Nov 18 05​:23​:56 2015, bartolin@​gmx.de wrote​:

I fudged some more tests with this error mode in S32-list/squish.t

The error happens in /src/core/Mu.pm when binding to @​a in the
signature of this sub definition​:

multi sub infix​:<eqv>(@​a, @​b) {
...
}

Moar and JVM behave differently when trying to bind a Seq in such a
case​:

$ perl6-m -e 'sub foo (@​a) { say @​a.WHAT }; my $a =
Seq.new((1..2).iterator); foo($a)'
(List)

$ perl6-j -e 'sub foo (@​a) { say @​a.WHAT }; my $a =
Seq.new((1..2).iterator); foo($a)'
Type check failed in binding @​a; expected Positional but got Seq
in sub foo at -e​:1
in block <unit> at -e​:1

This seems to be related to signature compilation on moar, which is NYI on jvm, cf. http://irclog.perlgeek.de/perl6/2015-11-20#i_11574866 and

00​:51 < psch> r​: use nqp; sub foo (@​a) { say @​a.WHAT }; my $a = Seq.new((1..2).iterator); foo(nqp​::decont($a))
00​:51 <+camelia> rakudo-moar, rakudo-jvm 0b6328​: OUTPUT«(List)␤»

@p6rt
Copy link
Author

p6rt commented Jul 16, 2016

From @usev6

Fixed with commit rakudo/rakudo@d09ad6eaf7

The tests are passing again. I'm closing this ticket as 'resolved'.

1 similar comment
@p6rt
Copy link
Author

p6rt commented Jul 16, 2016

From @usev6

Fixed with commit rakudo/rakudo@d09ad6eaf7

The tests are passing again. I'm closing this ticket as 'resolved'.

@p6rt
Copy link
Author

p6rt commented Jul 16, 2016

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

@p6rt p6rt closed this as completed Jul 16, 2016
@p6rt p6rt added glr JVM Related to Rakudo-JVM labels Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
glr JVM Related to Rakudo-JVM
Projects
None yet
Development

No branches or pull requests

1 participant