[perl #128059] Method-like thingies do not work with indirect object notation (&[leg] ‘a’: ‘b’)

2016-05-02 Thread via RT
# New Ticket Created by Alex Jakimenko # Please include the string: [perl #128059] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=128059 > This works: Code: say ‘a’.&[leg]: ‘b’ Result: Less But this does not: Code: say

[perl #128055] [PERF] Significant slowdown of multi-methods when the not-called one uses a "where" restriction.

2016-05-02 Thread via RT
# New Ticket Created by Calvin Schwenzfeier # Please include the string: [perl #128055] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=128055 > >From the #perl6 channel: cschwenz 8:46 p6: class Foo { multi method aaa() { my

[perl #128054] [BUG] In a string enclosed in parens, a {}-interpolation can't access the topic $_ of a statement modifier

2016-05-02 Thread via RT
# New Ticket Created by Sam S. # Please include the string: [perl #128054] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=128054 > Golfed example: say ("{$_}") for ; Expected behavior: Print the lines "aa" and "bb".

module citation index

2016-05-02 Thread Richard Hainsworth
To see which were the most used modules in the ecosystem, and to see how they developed over time, I developed a citation index. I've tracked the data on the modules.perl6.org site since the end of the last year, and put together some graphs. Here are the results:

[perl #122709] [PERF] await Promise in different thread

2016-05-02 Thread Will Coleda via RT
On Wed Apr 27 03:02:14 2016, lloyd.fo...@gmail.com wrote: > Now I'm at home I tried it on my Mac, I can confirm that: > > perl6 -e 'my $waiter = Proc::Async.new(:path, :args World>).start; await start { await $waiter }' > > prints Hello World and then hangs forever. > > On Wed, Apr 27, 2016 at

Re: [perl #128049] [BUG] "Cannot look up attributes in a type object" error has occurred in the context of using NativeCall

2016-05-02 Thread Brandon Allbery via RT
On Mon, May 2, 2016 at 9:20 AM, Elizabeth Mattijsen wrote: > > You should probably rename your method “new” to BUILD, so that the default > .new() implementation can find it. Could definition of a method new throw a worry or something, pointing people to BUILD and/or the object

Re: [perl #128049] [BUG] "Cannot look up attributes in a type object" error has occurred in the context of using NativeCall

2016-05-02 Thread Brandon Allbery
On Mon, May 2, 2016 at 9:20 AM, Elizabeth Mattijsen wrote: > > You should probably rename your method “new” to BUILD, so that the default > .new() implementation can find it. Could definition of a method new throw a worry or something, pointing people to BUILD and/or the object

Re: [perl #128049] [BUG] "Cannot look up attributes in a type object" error has occurred in the context of using NativeCall

2016-05-02 Thread Elizabeth Mattijsen via RT
> On 01 May 2016, at 16:43, Itsuki Toyota (via RT) > wrote: > > # New Ticket Created by Itsuki Toyota > # Please include the string: [perl #128049] > # in the subject line of all future correspondence about this issue. > #

Re: [perl #128049] [BUG] "Cannot look up attributes in a type object" error has occurred in the context of using NativeCall

2016-05-02 Thread Elizabeth Mattijsen
> On 01 May 2016, at 16:43, Itsuki Toyota (via RT) > wrote: > > # New Ticket Created by Itsuki Toyota > # Please include the string: [perl #128049] > # in the subject line of all future correspondence about this issue. > #

[perl #128050] "Cannot invoke this object" with comp_unit when using --rxtrace

2016-05-02 Thread via RT
# New Ticket Created by Salve J. Nilsen # Please include the string: [perl #128050] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=128050 > I'm using 2016.04-74-ga16f0a4: $ perl6 --rxtrace -e 'say "hello world"' Calling

[perl #128049] [BUG] "Cannot look up attributes in a type object" error has occurred in the context of using NativeCall

2016-05-02 Thread via RT
# New Ticket Created by Itsuki Toyota # Please include the string: [perl #128049] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=128049 > See the following results. $ perl6 -MNativeCall -e 'class Foo { has $.piyo; method

[perl6/specs] e094a6: Bring META format closer to reality

2016-05-02 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: e094a61055fc3d597b9870328fe598687bd49c03 https://github.com/perl6/specs/commit/e094a61055fc3d597b9870328fe598687bd49c03 Author: Jonathan Stowe Date: 2016-05-02 (Mon, 02 May 2016)

[perl #128048] Need command-line tool for reading embedded documentation

2016-05-02 Thread Tadeusz Sośnierz via RT
> I had better luck with: > > # > p6doc DBIish > # > > ... which produced results similar to that of 'perl6 --doc ' > in the original post, i.e., output to STDOUT, unpaged, sans 'man' > highlighting. > > So, partly this is a question of incorrect or misleading > documentation. Synopsis

Re: Where do I need to put a pm6 file?

2016-05-02 Thread Tadeusz Sośnierz
On 02/05/16 09:22, Fernando Santagata wrote: Nope. My fault: I didn't understand that the META* name ought to be either META6.json or META.info; I had it named META6.info (unhelpful error message, though). Indeed, it could provide something more informational if you clearly give it a local

Re: Where do I need to put a pm6 file?

2016-05-02 Thread Fernando Santagata
On Mon, May 2, 2016 at 8:56 AM, Fernando Santagata < nando.santag...@gmail.com> wrote: > On Sun, May 1, 2016 at 3:36 PM, Tadeusz Sośnierz > wrote: > >> Starting from the end: there's no need to use github, panda can install >> stuff just fine from a local directory :)

Re: Where do I need to put a pm6 file?

2016-05-02 Thread Fernando Santagata
On Sun, May 1, 2016 at 3:36 PM, Tadeusz Sośnierz wrote: > Starting from the end: there's no need to use github, panda can install > stuff just fine from a local directory :) > I've been not able to use panda to install a module from a local directory. I reinstalled