grondilu m: print qq{now is {now}} 00:05
camelia now is {now}
grondilu ^that seems wrong
m: print qq[now is {now}]
camelia now is Instant:1767485183.78389532
grondilu also: Happy New Year everyone :) 00:09
timo m: print qq{{now is {now}}} 00:18
camelia now is Instant:1767485961.779031394
timo m: print qq{now is {{now}}} 00:19
camelia now is {{now}}
timo you can have as many balanced nested separators as you like, but if you also want to have { } for interpolation you need to have at least {{ }} as the delimiters of your string
by which i meant to say you can have them balanced and be literal when your delimiters are { and } 00:20
not sure why exactly it is like that though? could be the nested delimiters thing overrides using bare { } for interpolation 00:21
grondilu might be more efficient to do it that way. No need to backtrack or something? 00:22
well actually no on second thought 00:23
so idk
it striked me as add though, as I don't recall any such peculiarity for qq{} before 00:24
*odd
also qq's doc does not seem to mention any of this 00:26
timo also, happy new year grondilu :)
would be great to have a doc ticket if there isn't one yet 00:27
grondilu should first be confirmed that it really is specced 00:33
(which I'm not convinced)
is there a way to test old raku versions? 00:34
(without checking out an old commit and recompiling that is)
timo of course, you can use the bots on the channel 00:37
committable6: releases print qq{pi is {pi}}
using "now" is not recommended when it can't differentiate by exit code 00:38
committable6 timo, ¦releases (96 commits): «pi is {pi}»
timo well, it's at least been in there a very long time 00:43
[Coke] if it can't check by exit code, it'll compare output 00:55
timo that's what i meant. but if you use "now" it won't have any that are not different from another 00:57
[Coke] oh, right] 01:03
01:29 arkiuat left 01:43 arkiuat joined 01:47 arkiuat left 02:11 arkiuat joined 02:23 hulk joined 02:25 kylese left 03:15 hulk left, kylese joined 03:37 stanrifkin joined 03:40 stanrifkin left 05:59 wayland joined, wayland76 left 07:19 Aedil left 10:00 abraxxa joined 10:03 arkiuat left 10:05 arkiuat joined
disbot8 <librasteve> fwiw, I’m with timo on keeping NQP out of the raku docs … the docs are already <<too much information>> imo 10:15
<librasteve> compared to eg Kernighan + Ritchie 10:16
<librasteve> SmokeMachine: I sincerely hope that you will decide to contribute to the exemplar work, formally this will all be published under the Artistic license 2.0, same as raku core and the majority of Raku modules 10:18
<librasteve> such as Red 10:19
wayland I agree about keeping NQP out of the Raku docs. It might be useful to have a link to *something* about NQP, possibly on the Slangs page. I have a feeling I ran across a PDF (maybe by jnthn) on Raku internals that might've been relevant here, but can't locate it just at the moment. 10:38
11:04 abraxxa left 11:05 Sgeo left
wayland I have a grammar, and I'm using Slangify. The grammar loads fine, and I can introspect it and see that it contains the rules I expect. However, I don't know whether Raku is actually using it after I use Slangify. Is there a way I can introspect that? 12:14
lizmat what does $*LANG say at compile time? 12:15
wayland Method Perl6::Grammar+{PackageDeclarator}.gist not found 12:18
(That's from BEGIN { say $*LANG; }
lizmat m: say BEGIN $*LANG.slang_grammar("MAIN").^name
camelia Perl6::Grammar
lizmat and that ? 12:19
with Slang::Emoji loaded that says: Perl6::Grammar+{Emoji} for me
wayland Perl6::Grammar+{PackageDeclarator}
lizmat and is PackageDeclarator your slang ? 12:20
wayland It shouldn't be.
The Slang has "unit module" stuff in it though. 12:21
That might be the problem.
lizmat so what should it say you think ?
wayland Well, the grammar object is called Qwiratry::Template::Slang::TemplateGrammar
lizmat then it should probably say +{TemplateGrammar} 12:22
as it uses the shortname of any class 12:23
wayland Good to have know! So maybe the "unit module" business is the problem?
lizmat I would doubt that, as that is basically mostly a syntax feature 12:24
wayland Hmm. The grammar was also marked "is export". 12:25
lizmat that just affects whether it gets placed in the EXPORT stash 12:30
wayland I think I might've figured it out. There's a part elsewhere in the code that declares a custom declarator. I think that might be incompatible with Slangify or something. 12:42
When I get rid of that, it just says "Perl6::Grammar". I'm going to bed. Hopefully I'll get a chance to look at it later in the week. 12:46
12:48 Aedil joined 15:11 abraxxa joined 16:24 andinus left 16:31 andinus joined 16:45 xinming left 16:47 xinming joined 17:34 abraxxa left 18:24 abraxxa joined 18:48 abraxxa left 19:00 stanrifkin joined 19:07 Sgeo joined
disbot8 <holmdunc> Huh, there's some SEO spammer making YouTube videos that have a plausible but generic intro, but in fact the videos are just auto-generated from StackOverflow content www.youtube.com/watch?v=VXIk2g4QlRg 19:28
<holmdunc> cdn.discordapp.com/attachments/633...25ec1&
<librasteve> @holmdunc thanks for the heads up - as part of the weekly, I do come across a handful of cr*p like this ... don't think that it has much traction 20:15
timo stackoverflow has a relatively permissive license, so it's not a big surprise that there's many schemes that literally just repackage the questions and comments in some way 20:17
20:30 stanrifkin left 20:48 euandreh joined
disbot8 <aruniecrisps> @wayland would you happen to be talking about this? edumentab.github.io/rakudo-and-nqp...s-day2.pdf 21:03
<aruniecrisps> Btw does Jonathan ever hop in here? I'd love to pick his brain some time 21:05
21:35 Aedil left 21:48 arkiuat left
librasteve_ .seen jnthn 22:11
tellable6 librasteve_, gist.github.com/5b19b4b41bff19e32a...faeb80a017
librasteve_ seen: jnthn
tellable6 librasteve_, gist.github.com/52a54e9d72737f61b9...6362f3e2cd
22:18 arkiuat joined
lizmat re: spammers making Youtube videos from SO questions: that has at least been going for a year of so now 23:08

Powered by Cro and the Raku® Programming Language.

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

Thank you!