🦋 Welcome to the MAIN() IRC channel of the Raku Programming Language (raku.org). Log available at irclogs.raku.org/raku/live.html . If you're a beginner, you can also check out the #raku-beginner channel!
Set by lizmat on 6 September 2022.
frost33 m: use experimental :rakuast; say 'say 100 + 200'.AST.statements.head.expression; 01:58
camelia RakuAST::Call::Name.new(
name => RakuAST::Name.from-identifier("say"),
args => RakuAST::ArgList.new(
RakuAST::ApplyInfix.new(
left => RakuAST::IntLiteral.new(100),
infix => RakuAST::Infix.new("+"),
right => RakuA…
frost33 So, now the "RAKUDO_RAKUAST=1" is not needed? 02:08
guifa_ frost: no 02:15
the RAKUDO_RAKUAST=1 is for having Rakudo's compiler et al using RakuAST as well
the RakuAST classes are enabled with the `use experimental` statemen 02:16
frost33 ok, I understand 02:20
librasteve okay - up with the larks at 05:15 - I have resolved the Nueric Delegation Issue here gist.github.com/librasteve/d9bf039...a8c7076ce3 04:56
nemokosch was almost right 04:57
lizmat was almost right
^^^ turns out you need BOTH!
Nemokosch Hm, wait. DataSlice shouldn't be coerced into Numeric at all. If you needed to do that, something is still not okay. 07:30
Unless you nest DataSlices, of course 07:31
librasteve I agree that .list is all you need for the [+] dss reduction 08:49
but I also want Numeric to yield data.elems for sums like dss + 1 08:50
Nemokosch okay but I'd imagine that's not needed for [+] dss to work, right? 08:51
librasteve yep - list is all you need 09:01
for that
further to that, I couldn;t figure why the resolved gist worked, but my code didn't ... I was using my \dss = $; then dss = x, dss = y, to save typing my all the time (durr) 09:20
after some tinkering (i) it is important that you do not use the my \dss = $; idiom since you need the container to not be a Scalar and (ii) the container role / class needs to do Iterable (but not Positional) 09:21
gist.github.com/librasteve/df48c92...a1871ae1eb is a new gist with that to play with 09:22
thanks for all the guidance
^^ which reinforces my opinion that it is pretty stupid to use any variable outside of $, @, %, & unless you are sure you know what you are doing 09:24
.tell tonyo (how) does fez support changing my username from p6steve to librasteve? 10:15
[Coke] (btw, my moarvm internal error was easily solved by adding a Lock.protect around the code touching the hash. This is the sort of thing where it might be nice to have some kind of doc for "hey, did you get this error (whether a standard exception or some weird internal panic) - then do this." 13:57
annoyingly, I had already had a my $lock = Lock.new before the race... and no protect call where it needed to be. didn't check git history, but weird. 13:58
uzl[m] .tell tonyo For this module, does adding Rakudoc/Pod6 to the module itself and then generating the README from it add any value to the module? 15:37
raku.land/zef:tony-o/CSV::Parser
tellable6 uzl[m], I'll pass your message to tonyo
uzl[m] Kind of a low hanging fruit but I think the community should start an effort to rename modules and whatnot to reflect the renaming, which is mostly extensions I'd assume 🙂 15:39
[Coke] as someone who works with docs, I understand the theoretical benefit of eating our own dogfood (writing docs in rakudoc) rather than having the source in markdown... but I am so used to markdown it feels like extra work. 15:43
uzl[m] <tbrowder__> "where/when is the raku core conf..." <- I didn't see an answer so resurfacing tbrowder's question :) 15:44
[Coke] benefit comes when we install the docs and can use something like rakudoc to read them, but I don't know how common that is yet.
dakkar [Coke]: I feel it's a bit of a bootstrapping problem ☺ 15:45
uzl[m] >but I am so used to markdown it feels like extra work.
No, I think this is fair but it's hard to encourage newcomers to use something when even community members don't use it haha
* > but I am so used to markdown it feels like extra work.
No, I think this is fair but it's hard to encourage newcomers to use something when even community members don't use it haha
dakkar rakudoc (which, IIRC, it's not part of the base rakudo distribution) is less useful/used because there's not much installed documentation 15:46
uzl[m] For me, it's an extra step
dakkar and there's not much installed documentation because "nobody uses rakudoc"
(that's my feeling, at least)
uzl[m] Btw there's Podlite (github.com/podlite/podlite-web) for rendering Pod which I haven't tried yet
A catch-22 type of situation lol 15:47
dakkar re: podlite, I find it funny that it's written in javascript, not raku
uzl[m] One day!!! 15:48
dakkar (ok, typescript, but still)
uzl[m] [Coke]: Whenever you get the chance, do you mind looking at github.com/Raku/doc/pull/4315? I also left some comments to close some issues that I think were addressed already :) 15:49
Ok back to work... until later 15:50
lizmat fwiw, App::Mi6 automatically creates a README from the rakudoc of the main file 15:59
it's not extra work for me
Nemokosch uzl[m] thank you very much, I raised similar concerns a while ago, it's not that we are helicopters probably 16:10
you just cannot make people care
presenting a consistent picture, e.g using consistent extensions, would really ONLY be a matter of discipline 16:11
dakkar should we re-invent kwalitee? it mostly worked for cpan… 16:16
(a distribution gets points for things like correct naming, tests, readme, changelog, &c; publish a leaderboard; gamify the whole thing) 16:17
Nemokosch for podlite: I think there is a positive way to look at it 16:18
1. it doesn't depend on, well let me be straight about it, the chaos revolving around Raku at all; it's an independent implementation, much like one could wish for Raku itself 16:19
2. it shows that somebody can be interested in this piece of technology without being in the "Raku camp" 16:20
3. in theory, being a "mundane" TS project could attract futher outsiders, the entry barrier is lower on average, see "why MoarVM is written in C" 16:23
jdv the renaming stuff will always be fraught. kwalitee may nudge some but i'm not sure its worth it unless you really want to do it:) 16:31
i'd be interested how important doc formats are to most people 16:33
at least as far as why they do or don't like/use raku 16:34
for me, its still performance - that's why i shy away from raku a lot of the time
jdv oh, and and a rather annoying memory leak - i forgot:( 16:42
tonyo what is the mechanism for pod -> md? 17:11
tellable6 2023-06-01T15:37:31Z #raku <uzl[m]> tonyo For this module, does adding Rakudoc/Pod6 to the module itself and then generating the README from it add any value to the module?
lizmat tonyo: raku.land/cpan:SOFTMOTH/Pod::To::Markdown 17:17
tonyo hmm adding a second pass to making documentation (rather than just writing it) is a hard sell for me
librasteve tonyo: is there a way to change username on fez? or should i make a new user and slowly migrate over? 19:42
[Coke] I feel like changing the username violates the auth setup! 20:31
lizmat I must agree with this librasteve 20:43
librasteve ok - thought I would ask 20:58
tonyo librasteve: new username and migrate is the right way so dists don't need to be modified/downstream users remain unaffected 21:09
a nice option too is to release another intermediate version letting people know to migrate 21:10
librasteve cool - many thanks! 21:10
timo matching changed user names seems like a thing a Recommendation Manager would want to do 21:17
tonyo it doesn't seem trivial to do. if librasteve changes to xyz and tony-o changes to librasteve then there's a resulting mess that requires a lot of other information to resolve. dates the names changed, dates dists were published, and all username changes between _any user_ with any of the usernames 21:40
using the groups mechanism seems like an alternative, then you maintain the user/group relationship 21:41
and you can publish with the name 21:42
s/(name)/group $1 21:43
tonyo , 23:21
uzl[m] .tell tonyo I've generated Markdown from Pod using Pod::To::Markdown, e.g., `raku --doc=Markdown lib/To/Class.rakumod`. re hard sell: I was planning to submit a PR taking care of that but I wanted to confirm it would be worth it before embarking on it 23:50
tellable6 uzl[m], I'll pass your message to tonyo
uzl[m] .tell <Nemokosch> re presentation and consistency: Right, for better or worse, first impressions do make a difference and since so much work has gone into Pod/Rakudoc, I think the least we can do is trying to use it. Obviously there are more pressing matters I'm sure though 23:54
tellable6 uzl[m], I cannot recognize this command. See wiki for some examples: github.com/Raku/whateverable/wiki/Tellable
uzl[m] Nemokosch: re presentation and consistency: Right, for better or worse, first impressions do make a difference and since so much work has gone into Pod/Rakudoc, I think the least we can do is trying to use it. Obviously there are more pressing matters I'm sure though 23:56
tellable6 uzl[m], I'll pass your message to Nemokosch

Powered by Cro and the Raku® Programming Language.

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

Thank you!