🦋 Welcome to the IRC channel of the core developers of the Raku Programming Language (raku.org #rakulang). This channel is logged for the purpose of history keeping about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | Logs available at irclogs.raku.org/raku-dev/live.html | For MoarVM see #moarvm
Set by lizmat on 8 June 2022.
00:07 reportable6 left 00:09 reportable6 joined 01:09 unicodable6 left, shareable6 left, reportable6 left, notable6 left, coverable6 left, tellable6 left, statisfiable6 left, committable6 left, sourceable6 left, linkable6 left, benchable6 left, quotable6 left, evalable6 left, bloatable6 left, squashable6 left, greppable6 left, releasable6 left, bisectable6 left, nativecallable6 left 01:10 committable6 joined, evalable6 joined, sourceable6 joined, shareable6 joined, linkable6 joined 01:11 quotable6 joined, reportable6 joined, squashable6 joined, bisectable6 joined, notable6 joined, unicodable6 joined, benchable6 joined, statisfiable6 joined, bloatable6 joined, coverable6 joined 01:12 tellable6 joined, releasable6 joined, greppable6 joined, nativecallable6 joined 03:32 frost joined 04:32 greppable6 left, statisfiable6 left, notable6 left, squashable6 left, sourceable6 left, coverable6 left, quotable6 left, linkable6 left, nativecallable6 left, tellable6 left, benchable6 left, committable6 left, shareable6 left, bisectable6 left, bloatable6 left, unicodable6 left, reportable6 left, evalable6 left, releasable6 left, shareable6 joined, releasable6 joined, evalable6 joined 04:33 squashable6 joined, greppable6 joined, nativecallable6 joined, unicodable6 joined, statisfiable6 joined, notable6 joined, committable6 joined 04:34 benchable6 joined, quotable6 joined, coverable6 joined, linkable6 joined, reportable6 joined, bloatable6 joined 04:35 sourceable6 joined, bisectable6 joined, tellable6 joined 05:35 statisfiable6 left, greppable6 left, notable6 left, bloatable6 left, committable6 left, bisectable6 left, nativecallable6 left, benchable6 left, unicodable6 left, releasable6 left, squashable6 left, evalable6 left, reportable6 left, tellable6 left, coverable6 left, shareable6 left, quotable6 left, linkable6 left, sourceable6 left, coverable6 joined 05:36 bloatable6 joined, unicodable6 joined, sourceable6 joined, evalable6 joined, squashable6 joined, quotable6 joined, greppable6 joined 05:37 benchable6 joined, nativecallable6 joined, releasable6 joined, tellable6 joined, bisectable6 joined 05:38 linkable6 joined, shareable6 joined, notable6 joined, statisfiable6 joined, reportable6 joined, committable6 joined 06:06 reportable6 left 06:08 reportable6 joined 09:09 linkable6 left, benchable6 left, committable6 left, nativecallable6 left, statisfiable6 left, sourceable6 left, notable6 left, coverable6 left, greppable6 left, bisectable6 left, shareable6 left, unicodable6 left, squashable6 left, evalable6 left, quotable6 left, releasable6 left, tellable6 left, bloatable6 left, releasable6 joined, shareable6 joined, sourceable6 joined, quotable6 joined 09:10 statisfiable6 joined, tellable6 joined, benchable6 joined, unicodable6 joined, nativecallable6 joined, greppable6 joined 09:11 squashable6 joined, bisectable6 joined, committable6 joined, notable6 joined, evalable6 joined, coverable6 joined 09:12 linkable6 joined, bloatable6 joined
Geth rakudo/lizmat-v-check: 493d9f3fd2 | (Elizabeth Mattijsen)++ | src/Perl6/Actions.nqp
Don't blindly make a Version object for vN

First look up whether there's a lexical symbol for it, and use that if we found it. Should fix #3919
rakudo: lizmat++ created pull request #5020:
Don't blindly make a Version object for vN
rakudo/lizmat-io-path-created: cc4a31735d | (Elizabeth Mattijsen)++ | 2 files
Add IO::Path.created returning the Instant a path was created

Or returns a Failure if the path does not exist. Why this wssn't done before, I don't quite understand, as the NQP support appears to exist on all backends.
rakudo: lizmat++ created pull request #5021:
Add `IO::Path.created` returning the `Instant` a path was created
10:40 sena_kun joined 10:55 frost left 11:19 [TuxCM] joined 11:30 Geth left 11:31 Geth joined 11:53 [TuxCM] left 12:05 [TuxCM] joined 12:07 reportable6 left, reportable6 joined 13:07 linkable6 left, evalable6 left 13:08 linkable6 joined, evalable6 joined 13:47 [TuxCM] left 14:00 [Coke]_ joined 14:02 [Coke] left 15:44 discord-raku-bot left, discord-raku-bot joined 15:50 discord-raku-bot left, discord-raku-bot joined 16:04 [TuxCM] joined 16:32 sena_kun left 17:09 atroxaper joined
atroxaper Hello! What do you think about Supply.interval(4 :between).tap(-> $ { #`[something longer then 4 seconds] }). I think that an inability to create in interval with delay between a tap execution is upsetting. 17:17
lizmat not sure what you mean: docs.raku.org/routine/interval 17:19
what is missing there?
atroxaper lizmat: Let's imagine that tap's lambda takes 5 seconds to execute. Then .interval(3).tap(...) will be executed every 5 seconds. But I want every 8 seconds. 17:25
lizmat you want it to wait 3 seconds after it having executed for 5 seconds 17:26
atroxaper Yes.
lizmat and if it happened to need 10 seconds for execution, then 3 on top of that ? 17:27
atroxaper yes.
lizmat do you have control on when something starts executing ? 17:28
atroxaper I even implemented it by custom Tappable class. But I want to consult is it good to add it to the Rakudo code.
lizmat well, if you want to make it a PR, then make it a PR, then you'll get the right consultation, also by people not necessarily on this channel 17:29
atroxaper I'm talking not about my problem, but about a general user problem - execute something with fixed delay between execution.
lizmat please make it a PR for more eyes :-) 17:30
atroxaper lizmat: OK. I thought irc is the first edge for such decisions :) 17:31
Going to make a PR.
lizmat yeah, please.. :-)
leont How do I force a moar rebuild when building a rakudo (I used --gen-moar in Configure) 17:57
18:06 reportable6 left 18:07 reportable6 joined
lizmat --force-rebuild 18:07
leont On Configure? 18:08
Yeah that seems to be doing something
lizmat afk& 18:14
18:29 [Coke]_ is now known as [Coke] 18:55 atroxaper left
patrickb o/ 19:52
20:20 discord-raku-bot left, discord-raku-bot joined 20:25 sena_kun joined
patrickb The Rakudo CI bot approaches the point where it becomes reasonable to target it at the live repos (instead of some test repos I have set up). 20:49
But it's probable it will not work flawlessly at first. Worst case are unhelpful CI test entries that are false negative or never turn green. 20:52
sena_kun patrickb, I am sure false positives are worse than false negatives. 20:57
I mean, if you have false positive for commit X and it's a flapper, the commit X+1 will complain, but if you have false positives people tend to ignore the whole system. 20:58
patrickb I guess both are possible. Point is: Should I "publish" early and basically force all devs to be testers, or continue developing in private with no one benefiting in the short run? 20:59
21:25 evalable6 left 21:28 evalable6 joined
sena_kun is not the core dev 21:40
patrickb, since all the repos are linked, I'm not sure if it's possible to do some sort of "partial" exposure? Say only moarvm. 21:41
21:41 sena_kun left 21:42 sena_kun left 21:51 pamplemousse joined
patrickb That should be possible. 22:03
\q 22:14
22:28 pamplemousse left 23:28 linkable6 left, evalable6 left 23:29 linkable6 joined 23:31 evalable6 joined 23:34 pamplemousse joined 23:42 pamplemousse left