> On 02 Oct 2016, at 11:00, Thor Michael Støre wrote:
> Is this normal startup performance?
https://www.promptworks.com/blog/public-keys-in-perl-6
I wonder what would be needed to run this in Perl 5, module wise, and CPU wise.
Liz
Yeah, it just got really noticeable when I had to run a relatively short script
over and over again, one that would have appeared to finish instantly on Perl
5. Startup time just stood out first since that’s about fifteen times higher on
6 vs stock 5. But I also see now that my full script has
recently, jnthn fixed a bug in attribute binding of natives in signatures, so
you should now be able to say:
submethod BUILD(uint64 :$!c, test1 :$!d) { } # should work, but doesn't
which in turn begs the question why you would need the BUILD anyway. But
indeed it looks like you need to do
On Mon, Oct 03, 2016 at 04:26:10PM +0200, Elizabeth Mattijsen wrote:
> > On 02 Oct 2016, at 11:00, Thor Michael Støre wrote:
> > Is this normal startup performance?
>
> https://www.promptworks.com/blog/public-keys-in-perl-6
>
> I wonder what would be needed to run this in
That is really lovely. I don’t know what criteria are used for Rosetta
Code, but the article’s implementation is the clearest “program as concrete
explication of algorithm” I’ve ever seen. It took me *years* to understand
RSA’s internals to the point that I could explain it if asked to in an
It seems like Moose vs built-in-oop/mop is a very indirect comparison. Now
I'm wondering what nqp or moarvm startups are like.
On Oct 3, 2016 06:14, "Elizabeth Mattijsen" wrote:
> > On 02 Oct 2016, at 11:00, Thor Michael Støre
> wrote:
> >
> > Hey
$ time install/bin/nqp -e ''
real0m0.025s
user0m0.017s
sys 0m0.006s
Liz
> On 03 Oct 2016, at 12:45, Brock Wilcox wrote:
>
> It seems like Moose vs built-in-oop/mop is a very indirect comparison. Now
> I'm wondering what nqp or moarvm startups are like.
On 2016-10-03 12:14, Elizabeth Mattijsen wrote:
Wrt to Pm’s timing of perl 5 with Moose: if you actually want to have
most of Perl 6’s capabilities in Perl 5 with Moose, you will need to
load quite a few MooseX:: classes as well. Which cannot have a
positive effect on load time.
Right. But
Looks like the solution is declaring the parameter type in the BUILD
submethod. This one works fine:
use NativeCall;
class test1 is repr('CStruct') is export {
has uint64 $.a;
has uint64 $.b;
}
class test2 is repr('CStruct') is export {
has uint64 $.c;
has test1 $.d;
submethod