|
00:01
librasteve_ left
|
|||
| jubilatious1_98524 | m: use v6.e.PREVIEW; my $x = Nil; say //$x; | 00:28 | |
| evalable6 | False | ||
| jubilatious1_98524 | m: use v6.e.PREVIEW; my $x = Nil; say !!$x; | 00:29 | |
| evalable6 | False | ||
| jubilatious1_98524 | m: use v6.e.PREVIEW; my $x = 0; say //$x; | 00:31 | |
| evalable6 | True | ||
| jubilatious1_98524 | m: use v6.e.PREVIEW; my $x = 1; say //$x; | ||
| evalable6 | True | ||
| jubilatious1_98524 | m: use v6.e.PREVIEW; my $x = 0; say !!$x; | 00:32 | |
| evalable6 | False | ||
| jubilatious1_98524 | m: use v6.e.PREVIEW; my $x = 1; say !!$x; | 00:33 | |
| evalable6 | True | ||
|
02:05
arkiuat left
02:15
arkiuat joined
02:56
lizmat joined
02:58
lizmat left
|
|||
| Geth | docker: 2d29409b26 | AntonOks++ | 6 files Bump to 2025.10 [skip workflow] |
03:12 | |
|
03:31
sibl joined
|
|||
| sibl | I am a big fan of simple tui IRC client, like ~delthas/senpai or osa1/tiny, is there any existing in Raku ? How doable would it be to make one using Terminal::UI ? | 03:36 | |
|
03:40
sibl left
03:48
azval joined,
azval left,
azval joined
03:49
sibl joined
04:57
Aedil joined
05:02
arkiuat left
05:04
lizmat joined
05:06
lizmat left
05:16
arkiuat joined
05:20
arkiuat left
05:26
arkiuat joined
05:30
derpydoo joined
05:34
Sgeo left
05:36
arkiuat left
05:38
lizmat joined
05:39
arkiuat joined,
lizmat left
05:46
arkiuat left
05:48
arkiuat joined
05:53
arkiuat left
05:58
derpydoo left
06:00
lizmat joined,
lizmat left
06:11
Aedil left
06:14
arkiuat joined
06:19
apa_c joined,
arkiuat left
06:27
arkiuat joined
06:35
arkiuat left
06:45
arkiuat joined
06:47
apa_c left
06:50
arkiuat left
07:20
arkiuat joined
07:29
arkiuat left
07:47
mimosa_ joined
07:51
librasteve_ joined
|
|||
| librasteve | sibl: sounds to me like a great Raku project … I’m sure you will get help here if you run into snags | 07:52 | |
| sibl | well thats sure its not terribly hard project to make xD but I am not an expert as well, so far I made the UI in few lines with Terminal::UI, I just found IRC::Client from @lizmat, I will see if I can simply use this and glue it to the UI | 07:53 | |
| librasteve | .oO … well Raku is good for glue | 07:54 | |
|
07:57
arkiuat joined
08:02
Aedil joined,
arkiuat left
|
|||
| sibl | created a git repo, if anyone wanna follow how it will progress xD github.com/4zv4l/rirc | 08:05 | |
|
08:09
kylese joined,
kylese left
08:10
kylese joined
08:11
dakkar joined
08:30
lichtkind joined
08:32
arkiuat joined
08:37
arkiuat left
08:46
sibl left
09:05
arkiuat joined
09:11
arkiuat left
09:20
apa_c joined
09:23
arkiuat joined
09:28
arkiuat left
09:32
lizmat joined
09:33
lizmat left,
lizmat joined
09:34
lizmat_ joined,
lizmat left
09:35
lizmat_ left
09:36
lizmat joined
|
|||
| lizmat | . | 09:40 | |
| tellable6 | 2025-10-22T07:53:19Z #raku-dev <melezhik> lizmat: your eco-system-cache could be also useful if we pack it inside docker containers which would run actually tests | ||
|
09:40
lizmat left
09:56
arkiuat joined
10:01
arkiuat left,
sibl joined
10:12
apa_c left
10:30
arkiuat joined
|
|||
| Voldenet | sibl: very nice idea, and irc client plugins make it very easy to extend later | 10:32 | |
| I'm interested when it's ready | |||
|
10:37
rba left
10:38
rba joined
10:39
sibl left,
arkiuat left
|
|||
| librasteve | sibl: yeah I need an IRC client that remembers all the messages between logins, faiing that then something I can run 24x7 on my unix server and then ssh from my laptop | 10:47 | |
| tellable6 | librasteve, I'll pass your message to sibl | ||
|
10:49
kaskal- left,
kaskal joined
10:56
arkiuat joined
|
|||
| simon_sibl | I can add a logging system yeah, I’ll see how fast I can understand and glue IRC::Client For plugin system I’ve never made one, I guess the easiest is to simply eval some files but that sounds very insecure 😆 | 11:00 | |
|
11:01
arkiuat left
11:10
lizmat joined
11:11
Pixi` joined
11:14
Pixi left
11:15
arkiuat joined
|
|||
| librasteve | guess I just need to get in the habit of going to the IRC logs irclogs.raku.org/raku/live.html ... that said having that as viewable from my terminal in the context of the IRC client would be a killer feature! | 11:18 | |
|
11:19
lizmat left
11:24
arkiuat left
|
|||
| simon_sibl | The feature would be to log the messages when you’re connected right ? | 11:26 | |
| librasteve | one of the main reasons I have to juggle Discord and IRCcloud windows is that the IRCcloud app has an unpredicatable coverage of previous messages in the channel - the Discord experience which I value is to have a continuously scrollable and fully searchable message history regardless of my logged on status ... the standard terminal IRC client (irssi) only gives me the live chat. I would be happy to setup each channel I care | 11:30 | |
| about with a url to go fetch the chat history (or just to have that hardwired for raku channels) ;-) | |||
|
11:36
arkiuat joined
11:40
lizmat joined
11:41
arkiuat left
|
|||
| simon_sibl | oh I see, otherwise I was wondering how that would be possible xD if I can add a plugin system, can be added that way (per channel script to fetch and append the downloaded logs to the channel logs variable for example) | 11:41 | |
|
11:45
lizmat left
11:47
lizmat joined
11:58
lizmat left
12:09
arkiuat joined
12:14
arkiuat left
|
|||
| SmokeMachine | I never had any problem with the logs of IRCCloud, librasteve_ could you give some more details about that, please? | 12:34 | |
|
12:36
arkiuat joined
|
|||
| librasteve | well, I think its because of furstration that each time I logout my laptop (which I do a lot) when I log back in after some time, then I have to click to rejoin all the channels and the backlogs are not available for quite a long time - now you mention, I checked and I see that since I have been logged in a while I can now click to load more backlog (but htis is the first time that this has worked for me since by then I have | 12:37 | |
| opened Discord anyway) | |||
|
13:04
lichtkind left
13:32
human-blip left
13:33
human-blip joined
|
|||
| Geth | ¦ problem-solving: arkiuat assigned to coke Issue What makes C<unit> be too late? github.com/Raku/problem-solving/issues/501 | 13:59 | |
| arkiuat | heh, I totally did not intend to assign that to [Coke]: github did it automatically. I don't think it's even a docs issue; rather, it's consensus needed in order to resolve a blocked docs issue | 14:02 | |
|
14:03
ds7832 joined
|
|||
| arkiuat | I don't know how to undo it either, nor how to relabel it "consensus needed" | 14:04 | |
|
14:04
dakkar left
14:06
oodani left
|
|||
| arkiuat | oh, never mind: that's a rakudo-issues label, not a problem-solving-issues label | 14:07 | |
|
14:11
oodani joined
|
|||
| arkiuat | m: sub EXPORT {}; unit package Foo; | 14:15 | |
| camelia | ( no output ) | ||
| librasteve | Word from the perlistas ... There's a late push for an LPW this year. Also called the LPRW when they feel like it. www.londonperlworkshop.com/ There's a feedback mechanism on that page. | 14:17 | |
| weekly: www.londonperlworkshop.com/ | |||
| notable6 | librasteve, Noted! (weekly) | ||
| ugexe | i assume the unit thing is due to namespacing | 14:19 | |
| librasteve | yeah - I saw it recently - sub EXPORT cannot be within the package class | ||
| arkiuat | yeah, I'm just trying to make the docs less confusing | 14:20 | |
| I opened the problem-solving issue because the related docs issue is seven years old and has been in blocked status for almost two years | 14:21 | ||
| librasteve | note this is not the same as my package EXPORT::DEFAULT {...} which afaik can live within the class | ||
|
14:21
dakkar joined
|
|||
| arkuiat: ++ | 14:21 | ||
| ugexe | I'd also guess that allowing arbitrary subs before unit is a rakudo quirk, not design | ||
| librasteve | personally I would be happy to outlaw combining unit and sub EXPORT - but then I am not a big user of unit | 14:22 | |
| arkiuat | that would be my guess too, but I don't think we have anything in ROAST to make sure that only a sub named EXPORT is allowed beforehand | ||
| librasteve | whatever is decided we should probably add to ROAST | ||
| arkiuat | well, that would break code, librasteve, since it has never been outlawed before | 14:23 | |
| librasteve | then deprecate now and release in 6.e | ||
| (??) | |||
| arkiuat | disallowing unit packages to use EXPORT seems kind of arbitrary to me (I do use unit) | ||
| librasteve | OK - fair enough. So lets just go with the flow - but add the current rakudo behaviour as a ROAST test from 6.e. | 14:26 | |
|
14:33
Sgeo joined
14:56
arkiuat left
15:02
ds7832 left
15:03
ds7832 joined
15:09
arkiuat joined
15:26
apa_c joined
15:52
lichtkind joined,
ds7832 left
15:54
ds7832 joined
16:08
itaipu left
16:17
itaipu joined
16:26
sjn left
16:27
itaipu left,
sjn joined
16:32
itaipu joined
16:34
ds7832 left
16:35
dakkar left
16:37
ds7832 joined
16:49
merp left
17:13
itaipu left
17:38
ds7832 left
17:41
ds7832 joined
17:51
ds7832 left
17:55
El_Che left
17:57
El_Che joined
|
|||
| m_zero | is there a difference between @a[3] and @a.[3]? They seem to produce the same results. | 17:59 | |
| (similarly for %a{'x'} and %a.{'x'}) | 18:00 | ||
| arkiuat | I think they're exactly equivalent | 18:15 | |
| basically subscripting is treated as a special kind of method call, I think? | |||
| Voldenet | > diff <(raku --target=ast -e 'my @a; @a[3]') <(raku --target=ast -e 'my @a; @a.[3]') | ||
| see for yourself | |||
| the difference in diff is basically only text, not operations | 18:16 | ||
| same with {} | |||
| arkiuat | Voldenet++ | 18:17 | |
|
18:19
LainIwakura joined
18:24
LainIwakura left
18:46
arkiuat left
18:52
ds7832 joined
18:53
orangebot joined
18:58
arkiuat joined
19:04
mimosa_ left,
Aedil left
19:06
mimosa_ joined
19:22
ds7832 left
19:24
mimosa_ left
19:32
lichtkind_ joined,
vrurg_ joined
19:34
coverable6__ joined
19:35
committable6__ joined
19:36
ntv joined,
avuserow_ joined
19:38
ds7832 joined
19:40
LainIwakura joined
19:41
lichtkind left,
swaggboi left,
coverable6 left,
committable6 left,
apogee_ntv left,
avuserow left,
vrurg left,
camelia left
19:43
LainIwakura left
19:44
LainIwakura joined
19:48
swaggboi joined
19:52
LainIwakura left
19:54
LainIwakura joined
19:55
lizmat joined
20:21
lizmat_ joined,
lizmat left
|
|||
| [Coke] | (irc session) I have an old mac mini I leave on all the time, then ssh into that when I want to IRC so the session is always running in tmux | 20:39 | |
| (and I have that port available externally as well so I can still IRC while I travel) | |||
| librasteve | lol - I just dumped my old mac mini fileserver ... | 20:40 | |
| (had loaded ubuntu and so on ... but still needed some tending) | 20:41 | ||
|
20:45
LainIwakura left
|
|||
| ds7832 | In q-quoted strings, the syntax \qq[...] can apparently also be used with delimiters other than []. This apparently isn't required by any roast, though. Is this still intentional? In that case I would add a sentence to the documentation. | 20:55 | |
| m: my $var = 'foo'; say '<code>$var</code> is <var>\qq«$var.uc()»</var>'; | 20:56 | ||
| evalable6 | (exit code 1) ===SORRY!=== Couldn't find termin… |
||
| ds7832, Full output: gist.github.com/3916448341fae34e38...63497960e3 | |||
| ds7832 | okay, «» doesn't work, but with {} or <> it does: | 20:57 | |
| m: my $var = 'foo'; say '<code>$var</code> is <var>\qq{{{$var.uc()}}}</var>'; | 20:58 | ||
| evalable6 | <code>$var</code> is <var>FOO</var> | ||
| librasteve_ | sorry I don’t understand … | 21:00 | |
| ds7832 | and in fact, «» also works, as long as ther closing deliminter isn't used ambiguously: | 21:01 | |
| my $var = 'foo'; say '<code>$var</code> is <var>\qq«{$var}»</var>'; | |||
| evalable6 | <code>$var</code> is <var>foo</var> | ||
| ds7832 | m: my $var = 'foo'; say '<code>$var</code> is <var>\qq«{$var}»</var>'; | ||
| evalable6 | <code>$var</code> is <var>foo</var> | ||
| ds7832 | librasteve_: Currently the documentation (docs.raku.org/language/quoting#Escaping:_q) only gives the example of \qq[...] | 21:02 | |
| librasteve | link? | 21:03 | |
| ds7832 | With rakudo, delimiters other than [] work as well, e.g. {}, <>, or also «» (if used unambiguoisly) | ||
| librasteve | docs link? | ||
| i mean its a given in Q slang that any delimiter is ok ... so not sure what you are saying | 21:04 | ||
| ds7832 | librasteve: I hope the link from the message at 23:02 works. | 21:05 | |
| librasteve | nope | ||
| ds7832 | Yes I think it's very logical that other delims should work too | ||
| as | |||
| ah* | |||
| librasteve | need link to offending docs pls | ||
| ds7832 | docs.raku.org/language/quoting#Escaping:_q | ||
| librasteve | tx | ||
| hmmm | 21:06 | ||
| ds7832 | So it works and it seems right that it should work. Looking for confirmation though before adding it explicitly to the docs | 21:07 | |
| librasteve | no need to change the doc imo | ||
| do a PR and I can review | |||
| pls | 21:08 | ||
|
21:09
apa_c left
|
|||
| ds7832 | librasteve: added it to this PR: github.com/Raku/doc/pull/4678 | 21:09 | |
| last commit, only the part about qq quoting (the rest I'm pretty certain about) | 21:10 | ||
|
21:13
lizmat_ left
21:20
LainIwakura joined
21:46
LainIwakura left
|
|||
| ds7832 | have a good night, I'll come back tomorrow | 22:06 | |
|
22:06
ds7832 left
22:32
arkiuat left
22:43
LainIwakura joined
22:46
arkiuat joined
22:50
arkiuat left
22:52
LainIwakura left
22:56
lichtkind_ left
22:59
kjp left
23:09
arkiuat joined
23:11
LainIwakura joined,
LainIwakura43 joined
23:17
librasteve_ left
23:27
LainIwakura left
23:31
LainIwakura43 left
|
|||