[perl #132531] Re: [BUG] type constraints to Array[Pair] don't work when precompiled

# New Ticket Created by Dan Zwell # Please include the string: [perl #132531] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132531 > I just checked, and got the same result on Rakudo version 2017.11 built on MoarVM version

[perl #127038] [POD] parsing does not create raw blocks

On Sat, 26 Dec 2015 14:27:04 -0800, autarch wrote: > There's a class in rakudo's Pod.pm named Pod::Raw, but rakudo does not > produce these blocks. I'm not sure whether the bug is that the class > exists or that it's never used. I *think* it's meant to be Pod::Block::Comment. In

[perl #132514] [JVM] Failing tests in S03-operators/set_*.t, probably wrong multi selected

On Tue, 28 Nov 2017 12:35:42 -0800, barto...@gmx.de wrote: > [...] > I tried to golf the failures from set_addition.t and found the > following: > > $ ./perl6-j --ll-exception -e ':<(+)>(SetHash.new, SetHash.new, > SetHash.new); :<(+)>(|(Set.new, Set.new, Set.new)); > :<(+)>(|(Set.new, Set.new,

Re: [perl #122838] [BUG] BEGIN GLOBAL:: assignment does not work in Rakudo

If you normally create a class, the entry in GLOBAL:: is decontainerized: $ 6 'class Test {}; use nqp; dd nqp::iscont(GLOBAL::)’ 0 However, if you just assign to a key in GLOBAL::, the result *is* containerized: $ 6 'BEGIN GLOBAL:: = class { }; use nqp; dd nqp::iscont(GLOBAL::)’ 1 So maybe you

Re: [perl #122838] [BUG] BEGIN GLOBAL:: assignment does not work in Rakudo

If you normally create a class, the entry in GLOBAL:: is decontainerized: $ 6 'class Test {}; use nqp; dd nqp::iscont(GLOBAL::)’ 0 However, if you just assign to a key in GLOBAL::, the result *is* containerized: $ 6 'BEGIN GLOBAL:: = class { }; use nqp; dd nqp::iscont(GLOBAL::)’ 1 So maybe you

[perl #118023] [BUG] typed hashes and metaops and slots, oh my, in Rakudo

So is the current behavior good or bad? On 2014-10-15 05:16:27, barto...@gmx.de wrote: > The current behaviour is: > > $ perl6-m -e 'my %h{Any}; %h=Any; %h //= "a"; say %h.perl' > Hash[Any,Any].new("a" => "a") > > $ perl6-m -e 'my %h{Any}; %h //= "a"; say %h.perl' > Hash[Any,Any].new("a" => "a")

[perl #123953] Coercion type applied via role parameter fails to multi-dispatch

On Sat, 28 Feb 2015 07:45:31 -0800, b...@abrij.org wrote: > (10:19:08 AM) skids: m: role g[::T $t] { multi method foo (T $a) { > "OHAI".say }; multi method foo($a) { "ONOES".say }; }; > g[Int(Str)].new.foo("100") > (10:19:09 AM) camelia: rakudo-moar 35de75: OUTPUT«ONOES␤» > (10:20:59 AM) jnthn:

[perl #122972] [NYI] Proto regex with params isn't called correctly (possibly NYI) in Rakudo

Still NYI (2017.11,HEAD(e5b660e)) On 2014-10-14 01:02:45, masak wrote: > m: grammar Test { token TOP { }; proto token > Foo(Int) {*}; token Foo:sym(Int $a) { "a" }; token Foo:sym(Int > $a) { "b" } }; say Test.parse("a"); > rakudo-moar 8b3e8c: OUTPUT«Too few positionals passed; >

[perl #122992] [BUG] Declaring a 'my' array or hash typed with a type parameter ends up blowing up with a fixable error message about instantiating generics in Rakudo

Seems to be reproducible (2017.11,HEAD(e5b660e)) On 2014-10-16 13:43:34, masak wrote: > camelia was having some indigestion in the below backlog, which is why > I'm reporting some local evals (from "This is perl6 version > 2014.09-202-g8b3e8c2 built on MoarVM version 2014.09-54-g03ac9a7"). > >

[perl #125200] [Bug] parametric role generic type not resolving early enough?

Still reproducible (2017.11,HEAD(e5b660e)) On 2015-05-15 11:25:07, jdv79 wrote: > The first example there should have been: > > [jdv@wieldy ~]$ perl6 -e 'role Foo[::T] { has Int @.a }; say > Foo[Int].new.a.WHAT' > (Array[Int]) > [jdv@wieldy ~]$ perl6 -e 'role Foo[::T] { has T @.a }; say >

[perl #126030] Multi-dim hash loses track of leaf type

Still reproducible (2017.11,HEAD(e5b660e)) On 2015-09-09 22:28:41, larry wrote: > 22:22 < TimToady> m: my Bool %hash{*;*}; %hash{"a"; "b"} = True; > 22:22 <+camelia> rakudo-moar c54773: OUTPUT«Type check failed in assignment > to '%hash'; expected 'Bool' but got 'Hash'␤ in block > at

[perl #76744] [TODO] implement :dba adverbs in regexes

Related doc ticket (with some discussion): https://github.com/perl6/doc/issues/1695 On 2010-07-27 02:32:49, moritz wrote: > alpha supported :dba('rule name'), current Rakudo doesn't, but should.

Re: [perl #125964] [LTA] assigning to AOB List elem does not hint right

Fixed with c9699ab , tests needed. Please note that this currently breaks tests 55-56 in S02-types/range.t which appear to be a little too specific for their own good. > On 3 Dec 2017, at 05:28, Aleks-Daniel Jakimenko-Aleksejev via RT > wrote: > > Today

Re: [perl #125964] [LTA] assigning to AOB List elem does not hint right

Fixed with c9699ab , tests needed. Please note that this currently breaks tests 55-56 in S02-types/range.t which appear to be a little too specific for their own good. > On 3 Dec 2017, at 05:28, Aleks-Daniel Jakimenko-Aleksejev via RT > wrote: > > Today

[perl #126116] [BUG] native type constraint inconsistently applied

Still reproducible (2017.11,HEAD(e5b660e)) On 2015-09-20 09:07:10, zef...@fysh.org wrote: > Because a type object is an (undefined) instance of that type, it can > in general be stored in a variable constrained to that type. We can > demonstrate this with a subroutine taking a type parameter: > >

[perl #123903] [BUG] Some forms of "dynamic symbol lookup" syntax cause compiler error in Rakudo

As of today (2017.11,HEAD(e5b660e)) it gives this: ===SORRY!=== Error while compiling -e Variable '$' is not declared at -e:1 --> say defined ⏏$:: There was another ticket that had exactly the same change of an error message, perhaps worth searching for it (ping me if you really want to

[perl #122838] [BUG] BEGIN GLOBAL:: assignment does not work in Rakudo

As of today (2017.11,HEAD(e5b660e)) it prints this: Cannot call method 'new' on a null object in block at -e line 1 Which is arguably reasonable, but I guess it's not good enough. On 2014-09-24 04:03:12, masak wrote: > m: BEGIN GLOBAL:: = class { }; Test.new; > rakudo-moar 682e03:

[perl #122991] [TODO] Implement 'handles' for 'my'-scoped (class) variables in classes

Still reproducible (2017.11,HEAD(e5b660e)) (complains about trait_mod:) On 2014-10-16 13:07:07, masak wrote: > m: class A { my @.foo handles }; A.push("OH", "HAI"); > say A.foo > rakudo-moar a6f181: OUTPUT«(timeout)» > locally: "Cannot call 'trait_mod:'; none of these > signatures match"

[perl #126107] [BUG] "of" type constraint inconsistently applied

All of these were fixed (2017.11,HEAD(e5b660e)). Strings give compile-time errors, putting Any into something results in an Int. Curious minds can ask bisectable for details. ｢testneeded｣ On 2015-09-20 17:26:00, zef...@fysh.org wrote: > Extended case: if the "of" clause comes after an "is

[perl #123835] Cannot use 'is rw' on optional parameter

Still reproducible (2017.11,HEAD(e5b660e)) I don't know if it's NYI or @LARRY. I'd put LARRY first, and then one of the LARRYs can turn it into a NYI. On 2015-08-05 15:25:57, barto...@gmx.de wrote: > The relevant sentences from the design docs (S06, introduced with > commit 7846594ee4): > >

[perl #116783] [BUG] 'my' class in role should be generic in Rakudo

Output on all releases: https://gist.github.com/Whateverable/297882f4f84bb8362a0ce0523439c436 On 2013-02-16 09:14:04, masak wrote: > r: https://gist.github.com/TimToady/4963642 > jnthn: that gets me an error Nominal type check failed for > parameter '$payload'; expected T but got Int instead >

[perl #110820] [BUG] Variable declaration inside statement_modifier for inside junction triggers bogus redeclaration error in Rakudo

This wasn't updated in a while. As of today (2017.11,HEAD(e5b660e)), it still complains about final ) like mentioned in one of the recent comments. And yes, this tickets seems to be rejectable. On 2015-07-20 09:27:25, duff wrote: > I'm not sure this is a bug. The postfix for is a statement

[perl #124007] [BUG] method delegation doesn't work in roles

Still reproducible (2017.11,HEAD(e5b660e)) On 2015-03-06 14:35:06, rayd...@cyberuniverses.com wrote: > As seen at http://irclog.perlgeek.de/perl6/2015-03-06#i_10237611 : > > r: role R { method foo () handles { } } > rakudo-moar 1b74e4: OUTPUT«===SORRY!=== Error while compiling >

[perl #125487] Possible MMD issue when binding nqp::null() ??

Still reproducible (2017.11,HEAD(e5b660e)) On 2015-06-26 02:25:27, elizabeth wrote: > [10:57:16] m: use nqp; my %h; %h := nqp::null() > #h > [10:57:16] <+camelia> rakudo-moar 3d645f: OUTPUT«Unexpected named > parameter 'BIND' passed␤ in block at /tmp/GYnIiEF0VO:1␤␤» > > This looks strange

[perl #120394] [BUG] Can't access private attributes through the ::('$!x') syntax in Rakudo

Still reproducible (2017.11,HEAD(e5b660e)) On 2013-10-28 02:49:38, masak wrote: > p: class A { has $!x = 42; method get() { ::('$!x') } }; say > A.new.get > rakudo-parrot 3cef56: OUTPUT«No such symbol '$!x' [...] > should that work? > moritz: my first thought is "I don't see why it

[perl #121166] [BUG] LTA error message when assigning to lexical variables from inside a regex in Rakudo

Still reproducible (2017.11,HEAD(e5b660e)), almost identical error message. On 2014-02-04 08:01:17, masak wrote: > m: my $x; 'abc' ~~ /$x=(ab)/; say $x > rakudo-moar 44ab3c: OUTPUT«===SORRY!===␤Error while > compiling op bind: QAST::Block with cuid cuid_1_1391529188.76986 has > not appeared␤» >

[perl #117421] [BUG] Typing with ::SomeClass instead of SomeClass in 'has' declaration causes the wrong type object to end up in that attribute in Rakudo

Still reproducible (2017.11,HEAD(e5b660e)) On 2013-03-30 16:55:04, masak wrote: > r: class A { has ::B $.b }; class B {}; print B.new; print > A.new.b.new > rakudo ba5e04: OUTPUT«B<-905822265>No such method 'new' for > invocant of type 'B'␤ in block at /tmp/TluLYMLqwz:1␤␤» > masak: ^^ hmm >

[perl #123507] Can't stat modules/debugger-ui-commandline/lib: No such file or directory

This is very old and nobody was complaining about this issue since then. I guess the problem is no longer there, but we won't be able to track it. Therefore, rejected (but I'm hoping that the underlying issue was actually resolved). On 2014-12-26 23:16:35, ga...@szabgab.com wrote: > During the

[perl #124226] [BUG] Opportunity to catch syntactically detectable calls to attribute-accessing methods on type objects in Rakudo

Still reproducible (2017.11,HEAD(e5b660e)) On 2015-04-01 13:19:33, masak wrote: > <[Tux]> m: class C { has Int $!x; method foo { ($!x, my $b) = > (1,2);}};C.foo > 19:45 <+camelia> rakudo-moar 6caf1d: OUTPUT«Cannot look up attributes > in a type object␤ in method foo [...] > <[Tux]> is that

[perl #125343] [WEIRD] Using an earliest { ... wait 0 { ... } } causes

Alright. On 2017-12-03 00:53:04, elizabeth wrote: > Those are predecessors of the “react / whenever” syntax. I think that > therefore this ticket can be closed now. > > > On 3 Dec 2017, at 04:58, Aleks-Daniel Jakimenko-Aleksejev via RT > > wrote: > > > > what is

Re: [perl #126099] [BUG] .WHICH fails for Block but True

Can be golfed to “Block but True”. Problem also existed for “Code but True”. Fixed with e31a414 . Tests needed. > On 3 Dec 2017, at 05:00, Aleks-Daniel Jakimenko-Aleksejev via RT > wrote: > > Still reproducible (2017.11,HEAD(e5b660e)) > > On 2015-09-18

Re: [perl #126099] [BUG] .WHICH fails for Block but True

Can be golfed to “Block but True”. Problem also existed for “Code but True”. Fixed with e31a414 . Tests needed. > On 3 Dec 2017, at 05:00, Aleks-Daniel Jakimenko-Aleksejev via RT > wrote: > > Still reproducible (2017.11,HEAD(e5b660e)) > > On 2015-09-18

Re: [perl #125343] Using an earliest { ... wait 0 { ... } } causes

Those are predecessors of the “react / whenever” syntax. I think that therefore this ticket can be closed now. > On 3 Dec 2017, at 04:58, Aleks-Daniel Jakimenko-Aleksejev via RT > wrote: > > what is `earliest`, `more` and `wait`? > > On 2015-06-06 16:40:28,

Re: [perl #125343] Using an earliest { ... wait 0 { ... } } causes

Those are predecessors of the “react / whenever” syntax. I think that therefore this ticket can be closed now. > On 3 Dec 2017, at 04:58, Aleks-Daniel Jakimenko-Aleksejev via RT > wrote: > > what is `earliest`, `more` and `wait`? > > On 2015-06-06 16:40:28,