PR was merged and test got added:
https://github.com/MoarVM/MoarVM/pull/357
https://github.com/perl6/roast/commit/67c494ced2
Thanks to all involved!
Fixed with:
https://github.com/MoarVM/MoarVM/commit/688796b434
https://github.com/rakudo/rakudo/commit/a92f092ac5
The error message now reads:
$ perl6 -e 'class Foo is repr { has Buf $.a }'
===SORRY!=== Error while compiling -e
CStruct representation only handles attributes of type:
(u)int8,
This issue is fixed if you configure MoarVM with --has-libffi as of today.
(You need of course the libffi-dev package installed.)
This bug is no more, closing.
You get 8 there because an array is a pointerish thing...
Btw, this:
my $not-null = CArray[int32].new
is not the same as this:
int a[3];
So, we would need fixed sized native arrays here to tell the truth.
Am 10.09.2016 um 20:53 schrieb Brandon Allbery via RT:
> On Sat, Sep 10, 2016 at
These patches fix and test the remaining issue:
https://github.com/rakudo/rakudo/commit/d0a00164e9
https://github.com/perl6/roast/commit/716b94f7ff
Hi, can I get verbose output please?
Patch: https://github.com/rakudo/rakudo/commit/42fb81d3b7
Tagging testneeded
As mentioned it is syntactically legal, therefore the syntax chek reports OK.
It fails at runtime though, which is to be expected.
A compiler time error always prints this as the first line:
===SORRY!===
As mentioned it is syntactically legal, therefore the syntax chek reports OK.
It fails at runtime though, which is to be expected.
A compiler time error always prints this as the first line:
===SORRY!===
Patch: https://github.com/MoarVM/MoarVM/commit/79dce1101b
I hesitate to put a test for this in...
Closing as resolved anyway.
Closing as resolved.
Patches and test:
https://github.com/MoarVM/MoarVM/commit/ada3752a81
https://github.com/rakudo/rakudo/commit/a8f407cccd
Resolving ticket as fixed.
Hi, can you please check if it is still broken?
The patch in https://github.com/rakudo/rakudo/commit/505dc4fa should fix it.
Hi, please consider using this slang which will most likely give you what you
need:
https://github.com/FROGGS/p6-Slang-Tuxic
But the short answer here is that the function call syntax wont change anymore.
Some examples that would break when we would change it:
if( # would not introduce a
Does that mean that we *always always always* have a gcc binary?
Can't we do something like this[^1] on darwin also?
[^1] https://github.com/MoarVM/MoarVM/blob/master/build/setup.pm#L445
Like, checking for the existance of clang, and falling back to gcc?
But the shown exit of "0" would be correct, no?
I guess we want to show more information when we cannot compile the test
scripts using the compiler we guessed
libuv does not like to build here, which is a dependency of MoarVM.
Though, that does not mean that we cannot do something about that.
Patches:
https://github.com/rakudo/rakudo/commit/2e4238fbe4
https://github.com/rakudo/rakudo/commit/0d5372fe43
Tests:
https://github.com/perl6/roast/commit/94ee230558
Closing ticket as resolved.
Patch: https://github.com/rakudo/rakudo/commit/95558bb58e
Tests: https://github.com/perl6/roast/commit/ff452eb56a
Closing as resolved.
I can confirm that the alignment is wrong.
To prove, I created this repo: https://github.com/FROGGS/p6-Gumbo
Running `perl6 t` gives:
~/dev/gumbo$ perl6 t/00-structure-sizes.t
1..19
ok 1 - sizeof(size_t)
ok 2 - sizeof(GumboStringPiece)
ok 3 - sizeof(GumboSourcePosition)
ok 4 - sizeof(GumboVector)
The fix for this misalignment is:
https://github.com/MoarVM/MoarVM/commit/7b382acd61
Test got added here: https://github.com/rakudo/rakudo/commit/deeec10a2e
Closing ticket as resolved.
The might be either this:
diff --git a/src/core/args.c b/src/core/args.c
index c4f2696..4772034 100644
--- a/src/core/args.c
+++ b/src/core/args.c
@@ -677,7 +677,7 @@ MVMObject * MVM_args_slurpy_named(MVMThreadContext *tc,
MVMArgProcContext *ctx)
static void flatten_args(MVMThreadContext *tc,
I did run this:
$ valgrind --leak-check=full --show-leak-kinds=all
/home/froggs/dev/nqp/install/bin/moar --execname="$0"
--libpath="/home/froggs/dev/nqp/install/share/nqp/lib"
--libpath="/home/froggs/dev/nqp/install/share/perl6/lib"
Patch: https://github.com/rakudo/rakudo/commit/6063886343
Test: https://github.com/perl6/roast/commit/2dfcd85181
Closing ticket.
Patch by bartolin++:
https://github.com/rakudo/rakudo/commit/4bdc88046ad0289f2708e3195e59df9edc83c258
Another test: https://github.com/perl6/roast/commit/1145029340
Closing ticket.
Patch: https://github.com/rakudo/rakudo/commit/6902d51eb7
Tests: https://github.com/perl6/roast/commit/7f43444370
Closing ticket.
Here are more examples (by novapatch++ via irc):
m: say «நி กำ षि "\r\n"»».chars
rakudo-moar cd7766: OUTPUT«(2 2 2 2)»
Patch: https://github.com/rakudo/rakudo/commit/5d83db3d01
Tests: https://github.com/perl6/roast/commit/51d1a4835f
Closing ticket.
Patch: https://github.com/rakudo/rakudo/commit/5d83db3d01
Tests: https://github.com/perl6/roast/commit/51d1a4835f
Closing ticket.
The design docs indicate that square brackets need to be used, which works with
rakudo:
constant $foo="+"; say :[$foo](3, 4)
rakudo-moar 4b1df7: OUTPUT«7»
So, this is closable with test?
The semantics of push got revised in the meantime, and a new method called
"append" got added:
m: my @a = 1,2,3; my @b; @b.push: @a,; dd @b
rakudo-moar fae01f: OUTPUT«Array @b = [[1, 2, 3],]»
m: my @a = 1,2,3; my @b; @b.push: @a; dd @b
rakudo-moar fae01f: OUTPUT«Array @b = [[1, 2, 3],]»
m:
Added test: https://github.com/perl6/roast/commit/f50149e607
Closing ticket.
Patch: https://github.com/rakudo/rakudo/commit/4b1df7b018
Tests: https://github.com/perl6/roast/commit/0478776107
Closing ticket.
Patches:
https://github.com/perl6/nqp/commit/41ab646099
https://github.com/rakudo/rakudo/commit/de4b2b3a87
Tests:
https://github.com/perl6/roast/commit/95ee3272ab
Closing ticket.
Patch: https://github.com/rakudo/rakudo/commit/32d7b08334
Tests: https://github.com/perl6/roast/commit/f665268fde
Closing ticket.
Patch: https://github.com/rakudo/rakudo/commit/32d7b08334
Tests: https://github.com/perl6/roast/commit/f665268fde
Closing ticket.
Patch: https://github.com/rakudo/rakudo/commit/32d7b08334
Tests: https://github.com/perl6/roast/commit/f665268fde
Closing ticket.
Patch: https://github.com/rakudo/rakudo/commit/32d7b08334
Tests: https://github.com/perl6/roast/commit/f665268fde
Closing ticket.
It seems to segfault in the op getlex when trying to locate
Moving sub foo to within the BEGIN block helps and moving it outside of A gives:
Cannot invoke this object
in method at lib/A.pm6:5
Neither the rakudo optimizer nor spesh seem to be to blame.
Seems to work now that we have DefiniteHOW:
m: sub a() returns Int:U { 42 }; say a
rakudo-moar 8f4e90: OUTPUT«(Int:U)Type check failed for return value; expected
Int:U but got Int in sub a at /tmp/LRo5pcMZof:1 in block at
/tmp/LRo5pcMZof:1»
m: sub a() returns Int:D { Int }; say a
Marked existing tests as related to this ticket:
https://github.com/perl6/roast/commit/5bd83c5b01
Closing ticket.
Patch: https://github.com/rakudo/rakudo/commit/80a3d07235
Tests: https://github.com/perl6/roast/commit/071720b28d
Closing ticket.
Patch: https://github.com/rakudo/rakudo/commit/8f4e908869
Test: https://github.com/perl6/roast/commit/f47d1dab1b
Closing ticket.
Design docs got aligned to rakudo so that method calls on blocks just do what
one would expect.
Patch: https://github.com/perl6/specs/commit/d1d502fb71
Tests: https://github.com/perl6/roast/commit/95a28225ed
Closing ticket.
Two more tests: https://github.com/perl6/roast/commit/51332a9ae1
I don't think that we should mix two concepts here.
The type constraint of an attribute just tells us what types/subsets are
allowed to be contained in the attribute.
That an attribute should be passed when instantiating an object (maybe passed
but undef?) is another story. And this has not
Added tests:
https://github.com/perl6/roast/commit/fca109de6c
https://github.com/perl6/roast/commit/6e66b7a18d
Closing ticket.
This fixes reporting the file and line number:
https://github.com/rakudo/rakudo/commit/164953b3de
This fixes it:
https://github.com/rakudo/rakudo/commit/164953b3de
Tagging testneeded.
Test: https://github.com/perl6/roast/commit/73fc8c3d37
Closing ticket.
Patch: https://github.com/rakudo/rakudo/commit/8dd74406e6
Tagging testneeded.
jnthn: I think we want to do it at MOP level in the future, if nothing else for
speed.
jnthn: I think we should force an initializer on :D'd things. .new is a bad
default. Try this: `class C { has $.x = rand }; for ^5 { my C:D $foo; say
$foo.x }`
jnthn: also we totally drop the thing on the
I come to the conclusion that making $foo.="bar"() work is more useful than
complaining about a potential P5ism.
So, patch and tests are here:
https://github.com/rakudo/rakudo/commit/98d9b87aaa
https://github.com/perl6/roast/commit/5f82bde7e0
Closing ticket.
Patch: https://github.com/rakudo/rakudo/commit/f52f0db3fb
This is fixed so far.
Patches:
https://github.com/perl6/nqp/commit/ada83f20892d3d027a0ac5e537ab1b111db1968e
https://github.com/perl6/nqp/commit/8402ce098192cdfe57bd438781d9f1322f63273c
Fixed tests:
https://github.com/perl6/roast/commit/eec7994c1f
Hi, what does `which panda` output? I'd almost say that it cannot find
panda in path, and the apt suggestions fail on your box...
Ahh, it might be possible that panda's state will only be installed
using the Windows MSI on... err, Windows...
I'll check the star tarball on a linux later and report back.
Please retest with rakudo-star-2014.12.1-moar.msi.
For me it gives this after a clean install of the msi:
C:\panda-m --installed list
Bailador [installed]
DBIish [installed]
Debugger::UI::CommandLine [installed]
Digest::MD5[installed]
what is your panda --installed list?
61 matches
Mail list logo
