🦋 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:00 reportable6 left 00:02 reportable6 joined 06:00 reportable6 left 06:02 reportable6 joined 06:48 sena_kun joined 08:11 squashable6 left 08:13 squashable6 joined 08:58 squashable6 left, squashable6 joined
Geth roast: f81f6d83cf | (Elizabeth Mattijsen)++ | S26-documentation/04-code.t
Fix implicit code block tests

  - marked as TODO for now
  - github.com/finanalyst/Rakudoc-BETA...1639120735		 09:26
roast: 2bad65a76a | (Elizabeth Mattijsen)++ | S26-documentation/01-delimited.t
Remove bogus tests

  github.com/finanalyst/Rakudoc-BETA...1639120735
established that all of those paragraphs are implicit code blocks, because abbreviated blocks such as =head1 do *not* set the margin		 09:33
12:00 reportable6 left 12:01 reportable6 joined
[Coke] I wonder if some kind of overall project plan-style document would be helpful. (what projects do people consider to be on their individual lists, are there dependencies, is there an overall plan that they are part of. 13:11
nemokosch Well, if it's not too much effort, it's almost certainly better to at least know where people are heading, even if there is no straightforward path to get there 14:28
I still think that an organized effort for tooling would be a game changer, with relatively little Raku-specific knowledge I guess 14:29
14:32 evalable6 left, linkable6 left, evalable6 joined 14:34 linkable6 joined
[Coke] What kind of tooling? 15:55
lizmat: is there a list of "these things must be completed before we can release 6.e"? I assume RakuAST is on that list, but not, e.g. "macro re-write in rakuast" 15:56
lizmat being able to build the core setting with the RakuAST grammar, is a hard prerequisite I'd say 16:19
16:23 evalable6 left, linkable6 left 16:24 evalable6 joined 16:25 linkable6 joined
[Coke] throws this against the wall: gist.github.com/coke/83ea82167f753...5e014e5c81 17:29
Comments and additions welcome
jdv i thought ast was a ways off from being stable 17:51
lizmat what has been implemented, has been pretty stable
jdv doe that mean 6.e is "a ways off"?
i mean like not experimental, mostly done.
lizmat if you do: 'use v6.e.PREVIEW' it's already not experimental anymore :-) 17:55
or 'use v6.*'
[Coke] I imagine we need a changelog for 6.e itself 17:56
18:00 reportable6 left
lizmat yeah, that's going to be quite a job in of itself... but could be started now already 18:01
18:03 reportable6 joined
nemokosch I have vague recollections that it wasn't clear what will be a distinct RakuAST node and what simply a property of an existing node, there are things like this 18:05
I've said this before but it's better to not jinx that it's stable when probably clearing up the interface will be a much easier, yet more impactful part than getting to a working prototype 18:06
Re [Coke] tooling: highlighter, editor plugins, LSP, profiler, this sort of stuff 18:08
btw a cool "core hacker" tool that might come from RakuAST is a syntax-based grepper 18:09
18:13 squashable6 left 18:16 squashable6 joined 18:37 sena_kun left 18:38 sena_kun joined
[Coke] finds github.com/bscan/RakuNavigator 19:01
(speaking of LSP) 19:03
nemokosch yep, we talked about it a couple of times
19:38 evalable6 left, linkable6 left 19:39 evalable6 joined 19:40 linkable6 joined 21:38 sena_kun left 22:20 japhb left 22:38 japhb joined
Geth JSON-Unmarshal/add-some-safety: 4 commits pushed by (Vadim Belman)++ 23:09
JSON-Unmarshal: vrurg++ created pull request #6:
Add some safety		 23:13
23:29 MasterDuke joined 23:56 squashable6 left 23:57 squashable6 joined

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!