And then nobody mentions that `and` has low priority. Try `say 42 & 13` and
`say 42 and 13`.
Best regards,
Vadim Belman
> On Jun 30, 2023, at 9:45 AM, yary wrote:
>
> Most of Richard's parting suggestions I understand & agree with, but not
> this: " why a
project funding.
Third, developers would get separated between projects. Depending on how many
would leave the original product, the pace of development of both could be
slowed down by a factor of 2 or even more.
Best regards,
Vadim Belman
> On Jun 9, 2023, at 2:40 AM, İsmail Arılık wr
ather problematic. Unless some kind of voting
would display overwhelming majority of one party. ;)
Just to conclude, I'm not trying to prove something. Just sharing thoughts.
Best regards,
Vadim Belman
> On Mar 13, 2023, at 11:42 PM, rir wrote:
>
>
>undefine seen at:
>
There are little known operators `andthen`, `orelse`, `notandthen` (I always
forget about the latter one too). What you are looking for would be:
given $s { m/ $=\w+ / andthen ..say }
Or, if you want a named variable:
given ("aaa") { (my $m = m/$=\w+/) andthen $m..say }
Best rega
lf is, roughly saying, unused.
Best regards,
Vadim Belman
> On Dec 30, 2022, at 4:44 PM, Sean McAfee wrote:
>
> On Fri, Dec 30, 2022 at 4:12 PM The Sidhekin <mailto:sidhe...@gmail.com>> wrote:
>> On Fri, Dec 30, 2022 at 8:51 PM Vadim Belman > <mailto:vr...@lflat.org&g
It is not "untrue". The sequence you produced goes nowhere. Thus the sink
context.
Best regards,
Vadim Belman
> On Dec 30, 2022, at 11:08 AM, Sean McAfee wrote:
>
> Ah, got it, thanks.
>
> It's mildly vexing, but the kind of side-effecty coding I described is
he code clarity doesn't suffer.
Best regards,
Vadim Belman
> On Dec 30, 2022, at 5:22 AM, Elizabeth Mattijsen wrote:
>
> if $s ~~ /$=[\w+]/ -> $/ { say $ }
>
>> On 30 Dec 2022, at 03:54, Vadim Belman wrote:
>>
>> Optimizations, yes... But then, how cou
y the regex eventually.
Best regards,
Vadim Belman
> On Dec 28, 2022, at 12:49 PM, Elizabeth Mattijsen wrote:
>
> That's because it at one time was decided that smart-match would set $/ in
> the caller's scope. Which is a pain for implementation and optimizations. I
>
&usg=AOvVaw2dFRaQG177YP-DaKPfw2a1>
Meeting ID: 868 0956 6554
Passcode: 540167
Happy coming New Year!
Best regards,
Vadim Belman
=vrurg01%40gmail.com
Comments are welcome on:
- Reddit:
https://www.reddit.com/r/rakulang/comments/z4qsnh/rakudo_coredev_class_announcement/
- Facebook:
https://www.facebook.com/groups/raku.perl6/permalink/3371142626485406/
Best regards,
Vadim Belman
I like the way you use ~ in `use lib '~/...';`. Though it doesn't work as
expected. But it's nice! :D
Best regards,
Vadim Belman
> On Oct 14, 2022, at 4:05 PM, Joseph Polanik wrote:
>
> On 10/14/22 3:38 PM, Elizabeth Mattijsen wrote:
>>> On
Looks like it worth a bug report. I was probably stumbling upon this too for a
couple of times.
Best regards,
Vadim Belman
> On Aug 27, 2022, at 2:24 AM, Fernando Santagata
> wrote:
>
> Hello,
> I noticed this behavior:
>
> [0] > my @a =
> [a b c d e]
is a makefile plus helper
scripts I include as a submodule for nearly each project I develop because mi6
doesn't cover my needs.
Best regards,
Vadim Belman
> On Jul 10, 2022, at 11:38 AM, Richard Hainsworth
> wrote:
>
> I have begun uploading modules to fez.
>
> Suppose a mod
How long ago v3.7.5 has been uploaded to p6c? Is p6c enabled in zef
configuration?
And it would be much better and more reliable to migrate to zef/fez ecosystem
already. :)
Best regards,
Vadim Belman
> On Jun 29, 2022, at 8:49 AM, Richard Hainsworth
> wrote:
>
> Hi,
>
>
considered deprecated.
Best regards,
Vadim Belman
> On May 3, 2022, at 11:59 AM, Marcel Timmerman wrote:
>
> Hi Brad,
>
>> Auth is for more than just the author. It is for author, authority, and
>> authentication.
> There is no password or other cryptographic way,
As long as I'm trying to follow topics, related to continuous testing with
github actions, I always see ubuntu-based scenarios. What about macOS and
Windows? Do we have rakudo images for these?
Best regards,
Vadim Belman
> On Jan 1, 2022, at 5:14 AM, JJ Merelo wrote:
>
> Try
rakudoc has been chosen as the official extension long ago.
Best regards,
Vadim Belman
> On Dec 30, 2021, at 11:13 AM, Tom Browder wrote:
>
> On Thu, Dec 30, 2021 at 06:26 Elizabeth Mattijsen <mailto:l...@dijkmat.nl>> wrote:
> +1 from me. Shouldn't that be a .r
I also agree that a page on docs would be helpful. But my point for this reply
is about renaming POD6. I don't think this makes much sense and barely would
ever happen. It is a legacy name, like NQP.
Best regards,
Vadim Belman
> On Dec 30, 2021, at 6:26 AM, Elizabeth Mattijse
There is no need to know about Raku development. It'd be enough to know Raku.
Best regards,
Vadim Belman
> On Nov 27, 2021, at 7:59 PM, Piper H wrote:
>
> I would like to be. But I know nothing about the development of Raku itself,
> so I most probably would be the product
You overlooked a mistype. The subset expects "wuhn", you pass "whun" instead.
Guess, the subset is wrong about it. :)
Best regards,
Vadim Belman
> On Sep 22, 2021, at 8:39 PM, Joseph Brenner wrote:
>
> In this code I'm using multi-dispatch with a subs
Hello Marc,
The best would be if you propose a PR or open an issue at
https://github.com/Raku/doc. Any help with the documentation would most
certainly be appreciated as people working on the docs project are overloaded.
Best regards,
Vadim Belman
> On Aug 25, 2021, at 8:09 AM, Marc Chantr
://conf.raku.org/talk/154 <https://conf.raku.org/talk/154>
https://conf.raku.org/talk/163 <https://conf.raku.org/talk/163>
Best regards,
Vadim Belman
> On Aug 22, 2021, at 8:57 AM, Marc Chantreux wrote:
>
> thanks everyone for sharing,
>
> Vadim,
>
> my ($a, $b) = { @
but still exclude it from
method dispatch when necessary.
Best regards,
Vadim Belman
> On Aug 21, 2021, at 2:03 PM, Joseph Brenner wrote:
>
> Given and example like this:
>
> class A {}
> class B is A {}
> class D is B {}
>
> say D.^parents(); # ((B) (A))
>
I guess you need something like this:
my ($a, $b) = { @^a[0,2...Inf], @a[1,3...Inf] }.(q<(){}[]>.comb); say $a; say $b
Best regards,
Vadim Belman
> On Aug 21, 2021, at 3:04 AM, Marc Chantreux wrote:
>
> hello,
>
> i would like to get the list of opening (α) and clo
ime? And how much sense would it make?
Best regards,
Vadim Belman
> On Jul 19, 2021, at 1:09 PM, Peter Scott wrote:
>
> Yes. I'm agnostic on this point, but there was a time when some prominent
> Perl contributors were dogmatic about it and I didn't know how widespread it
Let me guess. The school prohibits object self-initialization? It has to be
done by external code?
Best regards,
Vadim Belman
> On Jul 19, 2021, at 1:00 PM, Peter Scott wrote:
>
> On 7/19/2021 1:24 AM, Elizabeth Mattijsen wrote:
>> If .new wouldn't initialize
with no modifications or
copying.
Note that I say nothing to justify the use of ==>. I simply don't use it.
Best regards,
Vadim Belman
> On Jul 14, 2021, at 8:13 PM, Brad Gilbert wrote:
>
> Honestly I would advise against using ==> at the moment.
>
> For one thing
For the participants of TPRC2021:
Raku BOF session is scheduled for Wednesday, Jun 9, 18:00UTC. Zoom link is on
the Wiki page at https://github.com/perlconference/tprc-2021-cloud/wiki
See you tomorrow!
Best regards,
Vadim Belman
I think it is totally fine to post here. You could also try posting in
r/rakulang on reddit.
Best regards,
Vadim Belman
> On Jun 2, 2021, at 4:19 AM, Theo van den Heuvel wrote:
>
> Hi gurus,
>
> I consider hiring a raku consultant, but there does not seem to exist a raku
: there was a mistype and "taking" shoud've been
"talking". Sorry for this.
"Weird/will Ass Thing" made me totally lost as I've no idea what this means.
Best regards,
Vadim Belman
> On May 24, 2021, at 10:11 AM, Andy Bach wrote:
>
> my atomici
arently, this one is not ugly by semantics, but by its notation too. Also
worth noting that the hyper-op is needed here because pointy blocks are not
auto-threaded over junctions and take them as-is:
-> $v { say $v.WHAT }(1|2); # (Junction)
Best regards,
Vadim Belman
> On May 24, 2021,
it is true with eq which is a normal routine and Raku autothreads over it.
It still works well in conditions because they're boolean context and collapse
the resulting junction.
Best regards,
Vadim Belman
> On May 23, 2021, at 4:14 PM, Joseph Brenner wrote:
>
> Junctions cont
This:
$junction>>.say;
works the way it is because the junction is passed as an argument to the hyper
operator where the normal rules apply. Try it this way:
say $junction>>.say;
and it will result in:
a
b
c
any((True), (True), (True))
Best regards,
Vadim Belman
> On May 23
the call to find will not be auto-threaded.
Best regards,
Vadim Belman
> On May 21, 2021, at 4:41 PM, Joseph Brenner wrote:
>
>> I just gave a few other variants a try-- passing a junction in a
> variable, passing a code block containing a function-- without any
> luck.
>
>
For exact match one can use eqv:
say 1/10 eqv 0.1e0; # False
say 1/10*1e0 eqv 0.1e0; # True
Best regards,
Vadim Belman
> On Apr 6, 2021, at 7:25 PM, Ralph Mellor wrote:
>
>> 1/10 == 1e1 # True
>>
>> Aiui this is correct (and to me intuitive) behaviour described her
rtain cases. Third, it's first and foremost is a
personal project of Elizabeth, and I wish it remains this way because this is
one of the things which makes it so interesting and valuable.
Best regards,
Vadim Belman
> On Mar 14, 2021, at 7:30 AM, yary wrote:
>
> The Rakudo Weekly
The official one is what you get when go to docs.raku.org. I can hardly imagine
an acceptable way to have both versions represented under the same domain.
Best regards,
Vadim Belman
> On Mar 14, 2021, at 3:31 AM, Darren Duncan wrote:
>
> On 2021-03-13 2:27 p.m., Vadim Bel
documentation project could be among such topics.
Best regards,
Vadim Belman
> On Mar 14, 2021, at 3:25 AM, JJ Merelo wrote:
>
> I don't think it's a duplication (or, as might be the case, triplication) of
> resources, or a waste of resources. I learned early on that the &qu
At the first glance it looks like bug. Possibly a result of over-optimization.
Worth opening an issue at https://github.com/rakudo/rakudo/issues
Best regards,
Vadim Belman
> On Mar 13, 2021, at 3:29 PM, mimosin...@gmail.com wrote:
>
> Hi,
>
> When working with this week ch
e happy to see both project launched. One
could eventually become part of the official site, the other may be ran
independently. One way or another I hope there will be more gains from it than
loses.
Best regards,
Vadim Belman
> On Mar 13, 2021, at 2:21 AM, Richard Hainsworth
> wrote
n as one gains more experience with Raku it makes clear sense instantly.
Best regards,
Vadim Belman
> On Mar 2, 2021, at 9:26 AM, Parrot Raiser <1parr...@gmail.com> wrote:
>
>> Doing so would, of course, be a very bad idea. But still, you _could_.
>
> Something of an unde
is to see the
difference:
say Set.^methods.map: *.gist
say Set.^methods.map: *.name
Best regards,
Vadim Belman
> On Feb 16, 2021, at 3:38 PM, Gianni Ceccarelli wrote:
>
> On 2021-02-16 Joseph Brenner wrote:
>> But I don't see them in the list from .^methods:
>&g
foo;
say 4.VAR.^name; # Int
say @v[0].VAR.^name; # Scalar
Therefore, when you do @first = @both[0] – it is equivalent to @v = $a in the
first example.
We have a documentation section on this:
https://docs.raku.org/language/list#Itemization
Best regards,
Vadim Belman
> On Jan 19, 2021, at 1:1
g a List. It'd
be very confusing to get an Int instead!
Aside of this, the practice of returning so different values for rather similar
arguments doesn't look good for me.
Best regards,
Vadim Belman
> On Jan 19, 2021, at 11:07 AM, Fernando Santagata
> wrote:
>
> Hello,
easy to spot location. And it
will be there when our resources allow which must be read as: when somebody
find time to do it. Any help is welcome! :)
Best regards,
Vadim Belman
> On Jan 5, 2021, at 9:48 AM, Gianni Ceccarelli wrote:
>
> On 2021-01-05 Brad Gilbert wrote:
>> T
;
}
}
$midi-events can then be used in your react block. BTW, I think calling method
'poll' must not be needed because `read` should block until actual event is
available. At least this is how I understand the normal order of things.
Best regards,
Vadim Belman
> On Jan 1, 2021, at 1:
ide the comment.
Best regards,
Vadim Belman
> On Dec 22, 2020, at 7:59 PM, Parrot Raiser <1parr...@gmail.com> wrote:
>
> While playing around with the bounding characters for the #` form, I
> encountered an unexpected feature, which may or may not be a bug. If
> the left boundin
Unfortunately, neither rendered constraints nor image insertions are
implemented yet. Or it is so up to my knowledge, at least. I miss these
features too sometimes.
Best regards,
Vadim Belman
> On Aug 31, 2020, at 6:56 AM, Fernando Santagata
> wrote:
>
> Hello *,
>
&g
Oh, and the thing I forgot to mention: contrary to BUILD and TWEAK, DESTROY is
invoked by underlying backend VM. I.e. by MoarVM, or JVM, or JS because only
the VM knows when exactly an object cease to exists.
Best regards,
Vadim Belman
> On Jul 21, 2020, at 4:53 AM, Richard Hainswo
#x27;t use `$.attribute` notation though, only
`$!attribute` or `self.attribute`.
>
> 4) How to describe the way the TWEAK of a subclass accesses attributes in the
> parent?
It's done same way as accessing any parent method, as described above.
Best regards,
Vadim Belman
feature was planned. Another way is to link the files into ~/lib which is also
considered by macOS for executables under user's home dir.
Best regards,
Vadim Belman
> On Jul 10, 2020, at 10:00 PM, William Michels via perl6-users
> wrote:
>
> Hello,
>
> I just update
It doesn't have to be an assertion. Just a code block would do the same.
Best regards,
Vadim Belman
> On Jun 14, 2020, at 8:55 PM, Joseph Brenner wrote:
>
> $_ = "Alpha beta gamma";
> my @matches = m:g/(a) /;
necessary to have a Windows to test rakudobrew. I'm
mostly positive that you'd get same result on a linux to what you get with
appveyor.
Best regards,
Vadim Belman
> On Jun 13, 2020, at 5:34 PM, Richard Hainsworth
> wrote:
>
> Vadim,
>
> Your response is like a wh
rds,
Vadim Belman
> On Jun 13, 2020, at 4:57 AM, Richard Hainsworth
> wrote:
>
> Is the appveyor stanza (see the rakudobrew script below)
>
> - rakudobrew build moar %TEST_MOAR%
> the same as what you are suggesting?
>
> Richard
> On 13/06/2020 02:53, Vadim Belma
Not really sure about it, but don't you have to do 'rakudobrew switch
moar-%TEST_MOAR%' after building? rakudobrew doesn't immediately activates a
build.
Best regards,
Vadim Belman
> On Jun 12, 2020, at 4:03 PM, Richard Hainsworth
> wrote:
>
> I have t
ding, in a container shims are preferable over env.
Best regards,
Vadim Belman
> On Jun 12, 2020, at 2:40 PM, Elizabeth Mattijsen wrote:
>
> It is my understanding that rakudobrew has been renamed to rakubrew:
> https://rakubrew.org Could the be the issue?
>
>> On 12 Jun 202
more cumbersome. In either case, use of colons is not
always about saving a character or two. Sometimes it's about readability,
sometimes about elegance. Overuse is surely bad, but overuse of anything is
bad, for that matter. :)
Best regards,
Vadim Belman
> On Mar 17, 2020, at 1:09 PM, Joseph B
good example with a bit of Raku
charm:
class Foo {
has @.attr = ;
method foo { %(:@.attr) }
}
say Foo.new.foo; # {attr => [a b c]}
Best regards,
Vadim Belman
> On Mar 16, 2020, at 6:44 PM, Andy Bach wrote:
>
> Vadim clarified for us, off-list:
> > So, you basica
things.
Best regards,
Vadim Belman
> On Mar 15, 2020, at 5:41 PM, Andy Bach wrote:
>
> >> really means something like
> {* => (morerocks => [marble sandstone granite chert pumice limestone])}
>
> > Taking into account that => has tighter precedence than , what
the following data structure:
%( Whatever => Pair )
Regarding your use of postcircumfix [ ] on the data, you use it on Pair.
Best regards,
Vadim Belman
> On Mar 13, 2020, at 11:52 AM, Andy Bach wrote:
>
> > my %stash = monsters => @monsters, rocks => @rocks
> {
h the release of v6.e of
Raku language and removed in v6.f.
Best regards,
Vadim Belman
> On Mar 3, 2020, at 6:16 PM, Patrick Spek via perl6-users
> wrote:
>
> On Tue, 3 Mar 2020 16:41:47 -0500
> Parrot Raiser <1parr...@gmail.com <mailto:1parr...@gmail.com>> wrote:
>
{ ... } }
Best regards,
Vadim Belman
> On Jan 28, 2020, at 10:03 AM, Simon Proctor wrote:
>
> So some recent conversations covered the Range method on numeric types like
> Int
>
> So Int.Range gives the range of valid values -Inf^..^Inf which is neat.
>
> Then I thought I
At a quick glance, looks like a bug to me. Worth opening a ticket on
https://github.com/rakudo/rakudo
Best regards,
Vadim Belman
> On Jan 12, 2020, at 8:15 PM, Joseph Brenner wrote:
>
> Moving the definition of the subset outside of the class
> covers for the weird behavior
What rakudo compiler version do you use? Try 2019.11.
Best regards,
Vadim Belman
> On Dec 14, 2019, at 5:31 PM, Paul Procacci wrote:
>
> Ladies/Gents,
>
> I'm perplexed by the error message as stated in the subject.
> It's quite possible I'm doing it wron
st regards,
Vadim Belman
> On Dec 13, 2019, at 1:46 PM, ToddAndMargo via perl6-users
> wrote:
>
> On 2019-12-13 01:08, MT wrote:
>> In the light of renaming to Raku I was wondering if the statement 'use v6.*'
>> is still useful.
>
> Hi MT,
>
> If I a
about future language versioning are still possible. But
the final decision will not affect backward compatibility – see above.
Best regards,
Vadim Belman
> On Dec 13, 2019, at 4:08 AM, MT wrote:
>
> Hello all,
>
> In the light of renaming to Raku I was wondering if the statement
valid construct.
Best regards,
Vadim Belman
> On Nov 18, 2019, at 11:40 AM, yary wrote:
>
> I take that back! What is the dollar sign doing there in the '$.print: ..."
> example?
>
> Try it without the dollar sign. Right now you're calling .print on the
/zef>.
Respectively, for any other module from the ecosystem it's repo could be
located. I usually just google for it, but also
https://github.com/perl6/ecosystem <https://github.com/perl6/ecosystem> could
serve as a source of information.
Best regards,
Vadim Belman
> On Nov 6,
This is not really zef's "implementation detail". See rakudo sources in
src/core.c/CompUnit and grep for 'sha1'.
Best regards,
Vadim Belman
> On Nov 6, 2019, at 9:04 AM, Patrick Spek via perl6-users
> wrote:
>
> The problem is clearly with the Linenoise
,
Vadim Belman
> On Nov 5, 2019, at 7:15 PM, Parrot Raiser <1parr...@gmail.com> wrote:
>
> I'm treating this as a test of the process, reporting the problems
> created, so that the process can be fixed. Merely hacking up a
> solution might give me a better functioning
Hi Marcel,
Could you, please, open a ticket on github about this? Meanwhile, `perl6
--ll-exception` could possibly provide you with more details.
Best regards,
Vadim Belman
> On Oct 16, 2019, at 1:15 PM, Marcel Timmerman wrote:
>
> Hi,
>
> I've seen a LTA error message
Why would you need this? Mangling with things outside of your lexical scope
isn't one of the best ideas. Perhaps, you could achieve same result with simply
exporting the subset from the module using selective export with `is
export(:tag)`?
Best regards,
Vadim Belman
> On Sep 20, 2019,
&method);
}
class Foo {
has $.foo is xmlattr;
}
say Foo.new(foo => 42).foo;
It would output:
ATTR(foo):42
42
Best regards,
Vadim Belman
> On Sep 8, 2019, at 8:59 PM, Mark Devine wrote:
>
> Vadim,
>
> Vadim,
>
> Would you be able to expand on how to
usively internal needs of a class? If so, then the best
solution is to create a trait for an attribute and have it like:
has $.SerialNumber is xmlattr;
The trait would then install an accessor which would do what you need.
Best regards,
Vadim Belman
> On Sep 8, 2019, at 12:41 PM, Mark Devine
Hi Patrick,
I think any help would be useful with it. Perhaps, you could make a ticket on
https://github.com/rakudo/star/issues <https://github.com/rakudo/star/issues>
with your proposals.
Best regards,
Vadim Belman
> On Sep 3, 2019, at 3:03 AM, Patrick Spek via perl6-users
> wr
st regards,
Vadim Belman
> On Jul 8, 2019, at 11:42 AM, Parrot Raiser <1parr...@gmail.com> wrote:
>
> I've been fiddling with multi-line comments and the bounding
> characters. Naturally-paired characters e.g. #`(...) #`[...] #`{...}
> all work well, but with other
Not sure what you mean by 'leaking into CORE', but I wouldn't use Metamodel::
namespace too. My suggestion would be to use Type::SumHOW or
Type::Metamodel::SumHOW. The latter is better from namespace structuring point
of view unless long names disgust you.
Best regards,
Vadim B
Testing [OK] for Pod::To::Markdown:ver
>>> ===> Testing: Ddt:ver<0.5.5>:auth
>>> Failed to change the working directory to
>>> '/var/folders/r_/lk5svb150bzf2wdvp6ct_t_cgn/T/6aGzXY88az/Foo-Bar': does
>>> not exist
>>>
en even this
use case will be obsoleted.
So, to have a comprehensive fix for #2250 I need to know how to handle
submethods when a role is applied to a role: either I leave them untouched
where they're (and this would be my choice); or I get them copied alongside
with methods.
Best regards,
Vadim Belman
t_friend.greet;
> $best_friend.captivate($best_friend.^lookup('fiddle'));
>
> says
>
> Bow wow wow!
> tais toi!
> got sheet music, got rosin...
>
>
>
> I'm very happy with that behavior. Would like it to be documented.
>
> (And, I'll add comments to your bug tickets now)
> -y
Best regards,
Vadim Belman
ese were probably relatively simple cases). I
> don't really see why this should be considered as an anti pattern, although I
> can certainly feel that we should probably not try to ask too much from
> roles, the aim after all is to have something simpler than a class.
Best regards,
Vadim Belman
reply: isn't it constraining for the
purpose of constraining? To me Perl was always TMTOWTDI in first place. The
current approach to roles contradicts this principle.
Best regards,
Vadim Belman
; # LTA error. But with roles doing "flat" copying don't have an
> expectation that C knows the name "X",
> # I only expect that C can call method f which it got from Y, and that did
> work.
This looks reasonable. I would suggest you commenting on the bug report. It
would be useful to both the reporter and a core developer who's gonna consider
the report.
Best regards,
Vadim Belman
e problems, sooner or later!
Maybe somebody could explain clearly why things are the way they are now. I
would be very thankful for such information. Perhaps I need a tectonic shift in
my understanding of this area. But currently roles are the only thing which
really disappoints me in the language design.
Best regards,
Vadim Belman
https://github.com/perl6/Pod-To-HTML/issues/55> ?
> https://github.com/perl6/doc/issues/167
> <https://github.com/perl6/doc/issues/167> ?
> Somewhere else?
>
> --
> raiph
>
> On Mon, Jan 14, 2019 at 1:07 AM Vadim Belman <mailto:vr...@lflat.org>> wrote:
&g
, this will be the best approach for a
couple of years to come.
Best regards,
Vadim Belman
some in gitlab...
>
> Any suggestion is welcome, meanwhile.
>
> El sáb., 12 ene. 2019 a las 2:22, Vadim Belman ( <mailto:vr...@lflat.org>>) escribió:
> Hello,
>
> How do I properly write a link to a module in a POD documentation? Actually,
> the question
formats.
Best regards,
Vadim Belman
t; So my guess is that somehow during compilation, the MVMContext gets added to
> the SC (Serialization Context) when it shouldn’t.
>
> Most likely Timo Paulssen or Jonathan Worthington can give you better answers.
>
>> On 26 Dec 2018, at 04:26, Vadim Belman wrote:
>>
>>
es of adding a new package type were taken from World.nqp
add_package_declarator method which does some extra work some of which is
clearly not needed in my case; and some perhaps necessary but I don't
understand it yet.
Best regards,
Vadim Belman
7; error. So far, this is where I
stuck and would like to know if there is a workaround for this?
Basically, what I'm trying to achieve is could also be done by using a role as
a template which could then be applied to the custom class. But roles has a few
restrictions which would make them less flexible.
Best regards,
Vadim Belman
ack when I searched for large primes, HT gave a 25% speed boost.) So
> with 6 cores, 2 HT per core, I would expect a max parallel boost of 6
> * (1x +0.30x) = 7.8x - and your test is only giving half that.
>
> -y
>
Best regards,
Vadim Belman
(warning: too few iterations for a reliable count)
>>> workers5: 10.663 wallclock secs (36.983 usr 0.848 sys 37.831 cpu) @
>>> 0.094/s (n=1)
>>> (warning: too few iterations for a reliable count)
>>> O---O--O---
defined by the number of cores or, more correctly, by the number
of supported threads. Proving this hypothesis wold require more time than I
have on my hands right now. And not even sure if such proof ever makes sense.
Best regards,
Vadim Belman
pinned down this miraculous phenomenon
to .map. Any other code within LEAVE, including 'for' loop, makes the whole
thing to work as expected.
I'm strongly convinced that what is observed is a bug. But before reporting it
I'd like to make sure that there is nothing about .map that
> Thanks!
>
> --
> Fernando Santagata
Best regards,
Vadim Belman
al (see
>>>>> https://docs.perl6.org/type/Rat#Type_Graph)
>>>>>
>>>>> say Rat ~~ Real
>>>>>
>>>>> True
>>>>>
>>>>> Your're making a box that takes a Real, then putting
Real, return a Rat which
>is within $epsilon of that Real's value. Fail
>with X::Numeric::Real otherwise.
>
> And is this why I can not find a type "Rat"? Because
> it is a method?
>
> Then why does
>$ p6 'my Real $x; $x = 3.1415; dd $x;'
>Rat $x = 3.1415
> say it is a type "Rat"?
>
>
> Yours in confusion,
> -T
>
Best regards,
Vadim Belman
Actually, typing 'dd' in the searchbox on docs.perl6.org
<http://docs.perl6.org/> gives you a long list with dd in 'Reference' section
of that list.
>
> https://docs.perl6.org/routine/dd
> 404: Page Not Found
>
> Search does not work either.
>
Best regards,
Vadim Belman
also does
> > Real) into that box.
> >
> > It then says "yes, you've got a Rat in there".
> >
> >
>
> Why is it changing thing on the fly when I tell it not to?
> I claim foul !!AA HHH !!!
Best regards,
Vadim Belman
1 - 100 of 115 matches
Mail list logo