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
Array becomes string in subroutine or method calls #397
Comments
From @ilyabelikinHi there, sub foo (@a) { 1.say for @a } This one really pesky bug :( Ilya |
From @pmichaudOn Sat, Nov 08, 2008 at 12:54:52AM -0800, Ilya Belikin wrote:
I suspect this appeared as a result of the recent updates to Pm |
The RT System itself - Status changed from 'new' to 'open' |
From @moritzOn Sat Nov 08 09:32:09 2008, pmichaud wrote:
There are now tests for that in t/spec/S06-signature/passing-arrays.t moritz |
From @ilyabelikinThank you, very much! 2008/11/26 Moritz Lenz via RT <perl6-bugs-followup@perl.org>:
|
From @jnthnOn Sat Nov 08 09:32:09 2008, pmichaud wrote:
Bang on. There's a bit of a subtlety in that when we have a parameter we
I unfudged the ones moritz++ added. Thanks, Jonathan |
@jnthn - Status changed from 'open' to 'resolved' |
From @pmichaudUnfortunately I think this patch causes the following to fail: sub foo($a) { 1.say for $a } foo((1,2,3)); The problem is that simply looking at (misnamed) Perl6Scalar and We'll probably revisit this as part of updating parameter passing Pm |
@pmichaud - Status changed from 'resolved' to 'open' |
From @pmichaudOn Sat Nov 08 00:54:52 2008, ihrd wrote:
Now fixed as of r35392: $ ./parrot perl6.pbc Tests already exist in the suite, so closing ticket. Thanks! Pm |
@pmichaud - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#60404 (status was 'resolved')
Searchable as RT60404$
The text was updated successfully, but these errors were encountered: