|
🦋 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. |
|||
|
03:48
epony left
07:07
epony joined
08:13
samebchase joined
09:41
sena_kun joined
10:04
epony left
10:14
sena_kun left
10:15
patrickb joined
|
|||
| Geth | nqp/main: ea4385492d | (Elizabeth Mattijsen)++ | docs/ops.markdown Update list of possible nqp::const::xxx values |
12:50 | |
| [Coke] loves to see doc commits! | 13:24 | ||
| lizmat | :-) | 13:25 | |
|
13:36
epony joined
|
|||
| [Coke] | Do we need a doc test in rakudo/rakudo for the RAKUAST classes? | 13:56 | |
| (something simple like "is this class in the .md file) | 13:57 | ||
| lizmat | not yet | 14:25 | |
| in the past weeks I created two more classes :-) | |||
| [Coke] | I see some of the L10N module are copyright "Raku Localization Team" - I would recommend replacing that with an actual org like TRF (assuming they're OK with that) | 15:02 | |
| I defer to codesections on that. | |||
| lizmat: L10N::EN has an example of L10::NL | 15:04 | ||
| (without an explanation, and the use L10N::EN is in NL). Might be worth just a sentence explaining the structure of the example. | 15:05 | ||
| Geth | L10N/main: ac9aff7a5d | (Elizabeth Mattijsen)++ | 2 files Clarify example a bit, Coke++ |
15:09 | |
| lizmat | fwiw, I wanted something else than myself there | 15:10 | |
| (re copyright) | |||
| I specifically did not want to put TPRF there, as I feel that these localizations are independent of Rakudo | 15:11 | ||
| [Coke] | That's fair. I am nto a lawyer, it just seemed odd to have a not-actual org. | 15:14 | |
| lizmat | there's a github "L10N Maintainers" team :-) | 15:16 | |
| [Coke] | Ok, I withdraw my concern. :) | 15:17 | |
| lizmat | it only has one member as it stands, but still :-) | 15:26 | |
| Geth | rakudo/main: 1721f00b97 | (Elizabeth Mattijsen)++ | docs/dispatchers.md Finish initial stab at documenting MoarVM's dispatchers |
16:04 | |
| nqp/main: 022dec7fd4 | (Elizabeth Mattijsen)++ | 5 files Introduce nqp::track and nqp::guard These are short-cuts for: track('foo',…) nqp::dispatch('boot-syscall', 'dispatcher-track-foo', …) guard('foo',…) nqp::dispatch('boot-syscall', 'dispatcher-guard-foo', …) This should hopefully make the dispatcher setup code in core, as well as in Rakudo, a lot better readable. Also adjust most of the tests to use these new ops and add documentation for them |
17:23 | ||
| nqp/main: c29155bab5 | (Elizabeth Mattijsen)++ | 4 files Rebootstrap to get new track/guard ops |
|||
| nqp/main: e21eca7a69 | (Elizabeth Mattijsen)++ | 3 files Use new track / guard ops iternally as well |
17:36 | ||
| nqp/main: c53c163311 | (Elizabeth Mattijsen)++ | 10 files Reboostrap just in case |
|||
| rakudo/main: 2d8839e175 | (Elizabeth Mattijsen)++ | tools/templates/NQP_REVISION Bump NQP to get nqp::track/guard ops |
17:45 | ||
| rakudo/main: 1343953903 | (Elizabeth Mattijsen)++ | 3 files Use new nqp::track / nqp::guard ops Because after the bump we can. Plus a little streamlining for readability |
18:40 | ||
| rakudo/main: 5394496a28 | (Elizabeth Mattijsen)++ | docs/dispatchers.md Mention nqp::track/guard in dispatchers documentation |
18:41 | ||
|
18:45
p6steve joined
18:49
sena_kun joined
|
|||
| p6steve | o/ | 18:56 | |
|
18:57
librasteve joined
18:58
p6steve left
|
|||
| librasteve | remembers how to use irssi (barely) | 18:58 | |
| [Coke] has to google anything other than control-n. :) | 18:59 | ||
| librasteve | ++ decisions to close bridge to Discord and to moderate effectively | ||
| i propose closing the raku-dev and moarvm-dev sub Discords to avoid anyone mistaking them fo the thing (maybe pin a transition notice) | 19:02 | ||
| gfldex | They can be made readonly on the discord side. | 19:03 | |
| librasteve | hmmm - not sure - the other Disord channels remain and the mods are very lax ... I support (at least for now) keeping a Discord presence due to the ease of use and | 19:12 | |
| ... general popularity, so keeping the beginner and vanilla raku-irc channels bridged makes sense ... | 19:14 | ||
| ... but I think IRC only for the raku-dev, moar-dev channels is probably best rather than read only which feels a bit like the devs are more high and mighty | 19:16 | ||
| gfldex | good point | 19:17 | |
| librasteve | the raku-steering-council irc is there and bridged for community wide policy dissemination and debate for all | 19:19 | |
|
19:33
librasteve left
19:38
librasteve joined
19:50
librasteve left
19:58
librasteve joined
20:08
librasteve left
20:31
librasteve joined
20:36
librasteve left
22:17
sena_kun left
22:22
librasteve joined
22:28
librasteve left
22:33
librasteve joined
23:29
librasteve left
23:38
librasteve joined
23:44
librasteve left
|
|||