[00:08] *** reportable6 left [00:11] *** reportable6 joined [00:11] *** lichtkind left [00:21] *** raiph left [00:25] *** epony left [00:51] *** _ed joined [00:56] *** _ed left [00:58] *** _ed joined [01:03] *** _ed left [01:04] *** epony joined [01:17] *** _ed joined [01:22] *** _ed left [01:30] *** _ed joined [01:40] *** _ed left [02:24] *** _ed joined [02:28] *** _ed left [02:57] *** _ed joined [03:02] *** _ed left [03:40] *** clarjon1 left [03:49] *** squashable6 left [03:54] *** _ed joined [03:59] *** _ed left [04:26] *** euandreh left [04:30] *** energizer joined [04:30] *** energizer left [04:44] *** kj4tip left [04:45] *** kj4tip joined [04:51] *** squashable6 joined [04:53] *** euandreh joined [04:54] *** _ed joined [04:59] *** _ed left [05:02] *** kj4tip left [05:02] *** kj4tip joined [06:02] *** squashable6 left [06:02] *** committable6 left [06:02] *** bloatable6 left [06:02] *** coverable6 left [06:02] *** notable6 left [06:02] *** shareable6 left [06:02] *** sourceable6 left [06:02] *** bisectable6 left [06:02] *** unicodable6 left [06:02] *** greppable6 left [06:02] *** quotable6 left [06:02] *** evalable6 left [06:02] *** linkable6 left [06:02] *** benchable6 left [06:02] *** nativecallable6 left [06:02] *** statisfiable6 left [06:02] *** releasable6 left [06:02] *** reportable6 left [06:03] *** unicodable6 joined [06:03] *** releasable6 joined [06:03] *** statisfiable6 joined [06:04] *** linkable6 joined [06:04] *** evalable6 joined [06:04] *** reportable6 joined [06:04] *** coverable6 joined [06:04] *** sourceable6 joined [06:04] *** notable6 joined [06:05] *** shareable6 joined [06:05] *** greppable6 joined [06:16] *** kj4tip left [06:49] *** Sgeo_ left [06:53] *** sivoais_ left [06:54] *** sivoais joined [07:04] *** squashable6 joined [07:05] *** quotable6 joined [07:10] *** kj4tip joined [07:41] *** abraxxa joined [07:49] *** abraxxa left [07:50] *** abraxxa joined [08:03] *** bisectable6 joined [08:04] *** nativecallable6 joined [08:05] *** _ed joined [08:06] *** committable6 joined [08:10] *** _ed left [08:11] *** discord-raku-bot left [08:11] *** discord-raku-bot joined [08:37] *** _ed joined [08:43] *** _ed left [09:04] *** benchable6 joined [09:07] *** dakkar joined [09:12] *** Xliff left [09:50] *** _ed joined [09:54] *** _ed left [10:05] *** bloatable6 joined [10:12] *** wingfold joined [10:49] *** _ed joined [10:51] *** wingfold left [10:54] *** _ed left [11:06] *** razetime joined [12:00] *** euandreh left [12:07] *** wingfold joined [12:08] *** immediate joined [12:09] *** reportable6 left [12:12] *** linkable6 left [12:15] *** linkable6 joined [12:24] *** _ed joined [12:29] *** _ed left [13:03] ¦ problem-solving: 81cfdd3a23 | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | solutions/meta/sunsetting-p6c-cpan.md [13:03] ¦ problem-solving: Resolution: Preparing the Raku Ecosystem for the Future (#318) [13:03] ¦ problem-solving: [13:03] ¦ problem-solving: Resolution document for problem solving issue #316 [13:03] ¦ problem-solving: [13:03] ¦ problem-solving: https://github.com/Raku/problem-solving/issues/316 [13:03] ¦ problem-solving: review: https://github.com/Raku/problem-solving/commit/81cfdd3a23 [13:03] *** _ed joined [13:07] *** _ed left [13:12] *** reportable6 joined [13:22] *** xinming left [13:24] *** xinming joined [13:47] *** curiosa joined [13:55] *** curiosa left [14:02] *** curiosa joined [14:34] *** Sgeo joined [14:38] *** wingfold left [15:06] *** solitario left [15:07] *** solitario joined [15:10] *** solitario left [15:10] *** solitario joined [15:13] *** euandreh joined [15:14] *** solitario left [15:14] *** solitario joined [15:24] *** [Coke] left [15:27] *** euandreh left [15:27] *** _ed joined [15:28] *** [Coke] joined [15:28] *** euandreh joined [15:32] *** _ed left [15:41] *** kj4tip left [15:42] *** kj4tip joined [15:45] *** curiosa left [16:10] *** razetime left [17:01] *** _ed joined [17:07] *** _ed left [17:24] *** djerius left [17:25] *** djerius joined [17:31] *** _ed joined [17:35] *** dakkar left [17:39] *** _ed left [17:51] Is there a whenever equivalent to next? To skip the rest of the block? raku.org seems to be very much down [17:55] check out raku.guide [17:55] next [17:55] by the way, is rakudo's js backend usable for anything yet? [17:55] m: react { whenever 1 { say 42; next; say 43 }; whenever 2 { say 555 } } [17:55] rakudo-moar 90d876a3f: OUTPUT: «42␤555␤» [17:56] and i take there's nothing analogue to clojurescript built with the js backend yet? [17:59] though you can't use a label ala `FOO: react { whenever 1 { next FOO } }` [18:00] by the way, is goto ever getting implemented :V? [18:01] nqp is supposed to already have it but its not available with rakudo? [18:01] and now for a code question [18:01] how would i use thunks in raku? [18:03] i want to delay function evaluation by storing thunks inside a data structure [18:03] ie: an array of functions that will be called in sequence [18:03] so i can just push function calls inside the array and then call them [18:04] *** abraxxa left [18:10] *** reportable6 left [18:11] drakonis: Code is first class in Raku. Subs, Blocks, Routines of various sorts can all be treated as function pointers, and behave as closures. See https://github.com/japhb/Terminal-ANSIParser/blob/main/lib/Terminal/ANSIParser.rakumod for a rather aggressive example of building up function tables to create a state machine. [18:11] that's fantastic. [18:12] it solves the extensibility problem i had in mind for the automation framework i'm writing [18:13] pure raku, as opposed to sparrow's approach [18:19] which has been to shell out to subprocesses as much as possible [18:41] This website raku.org/ is currently offline. Cloudflare's Always Online™ shows a snapshot of this web page from the Internet Archive's Wayback Machine. To check for the live version, click Refresh. [18:41] ^ Getting that when visiting raku.org [18:42] uzl[m] I'm aware of it, trying to contact our infra team :-) [18:47] "uzl I'm aware of it, trying to..." <- Oh I see, thanks ;-) [18:52] *** _ed joined [18:56] *** _ed left [19:07] i'm not seeing the link to the wayback machine. guess i'll have to do it manually [19:08] Raku infra team is trying to find out why the server has become unreachable [19:08] wayback has gotten a lot snappier [19:09] ask putin [19:56] *** linkable6 left [19:56] *** evalable6 left [19:57] *** evalable6 joined [20:11] *** _ed joined [20:12] *** reportable6 joined [20:13] *** leah2_ joined [20:16] *** leah2 left [20:19] *** n1to joined [20:23] *** immediate left [20:33] *** n1to left [20:33] *** n1to joined [20:36] *** n1to left [20:39] *** n1to joined [20:39] *** ubq323 joined [20:44] *** leah2_ is now known as leah2 [20:44] *** p6steve joined [20:45] *** p6steve joined [20:45] <_ed> is raku.org down? [20:48] yeah... we're still trying to reach the right people [20:49] looks like its back up [20:49] <_ed> guess i'll just switch back to Ruby :_( [20:49] lol [20:50] not up for me :-( [20:50] showing a cached version from Wayback Machine [20:52] docs.raku.org appears to be up again [20:55] just *very* slow [20:56] ah, no, locally cached version :-( [20:56] *** linkable6 joined [21:01] *** _ed left [21:01] *** melezhik joined [21:01] . [21:02] *** sisar joined [21:03] *** _ed joined [21:03] update on raku.org: it appears a server move has gone awry [21:06] codesections: is there an status update on épee? [21:07] *** _ed left [21:10] Épée, rather. [21:10] raku.org and associated sites should be up again [21:10] fantastic. [21:11] thanks rba maettu nine ! [21:15] thx for those involved! [21:18] *** sisar left [21:20] *** _ed joined [21:23] I am contemplating on building ci server for Raku projects, I wonder if people are quite happy now with GH/Ado etc? I think I can build a solution that would be as close to Raku as possible with many features out of the box, but before starting anything ... I'd like if there is a niche for that ... [21:25] so right now people would write yet another yaml file with devopsih stuff init - like git repo info , zed install and maybe something else ... I am thinking that it's possible to build a solution where people would just point a git repo and that is it, setting all options via web UI [21:25] no yaml coding required at all [21:26] so eventually many features could be added without necessity to change anything on users side ... [21:27] like even now I am thinking about  adding App::RaCoCo test coverage out of the box [21:33] *** melezhik left [21:52] *** morte_ joined [22:13] drakonis: I'm not sure how far the JS will get, but I had it working decently well for a localized exceptions editor [22:14] i see [22:15] the problem is (at least doing things in browser) it takes a little bit for Rakudo to compile [22:15] That might not be a problem on node.js though? I haven't done anything there though to and dunno if it precompiles its modules [22:21] *** n1to left [22:21] I don't imagine it ultimately be used too terribly much on JS or JVM, but it not being pinned to any single VM has been very beneficial for the project in general, I think [22:25] *** _ed left [22:31] *** morte_ left [22:32] ¦ Raku-Steering-Council/main: 500c241101 | (Geoffrey Broadwell)++ | minutes/20220319.md [22:32] ¦ Raku-Steering-Council/main: Add RSC meeting minutes for 2022-03-19 [22:32] ¦ Raku-Steering-Council/main: review: https://github.com/Raku/Raku-Steering-Council/commit/500c241101 [22:36] *** _ed joined [22:46] *** _ed left [22:58] *** _ed joined [23:02] *** _ed left [23:07] *** _ed joined [23:13] *** _ed left [23:23] *** Juerd left [23:24] *** _ed joined [23:25] *** Juerd joined [23:40] *** melezhik joined [23:40] so ... a very prototype example of such a Raku ci system report could be - https://sparrowhub.io:4000/report/fastspec.notify/440 [23:41] *** Kaipi left [23:41] this build runs zef tests for Test::Async module checked out from GH repo [23:41] *** Kaiepi joined [23:42] also one can test coverage for this module made by App::RaCoCo [23:43] we can think about all other features included out of the box  by default ( not required any modifications from user side  ) - which are actual for any typical Raku project [23:44] even now for example it's possible to publish test coverage statistic in html format as App::RaCoCo already does that [23:45] so modules author would just register in this CI service and point their Github, Gitlab whatever source code urls [23:45] and that is it