00:03
ACfromTX joined
00:15
finanalyst left
00:23
ACfromTX left
00:25
ACfromTX joined
00:28
abraxxa-home left
01:16
Guest81 joined
01:39
Guest81 left
02:06
hulk joined
02:07
kylese left
02:09
Aedil joined
02:38
librasteve_ left
02:48
zenmov left
03:06
kst left
03:12
cm left
03:15
hulk left,
kylese joined
|
|||
[Coke] | raku.land/zef:tbrowder/PDF::NameTags | 03:20 | |
03:21
cm joined
03:32
kst joined
03:54
oodani left
03:55
oodani joined
04:00
oodani left
04:01
oodani joined
05:46
stackspace joined
06:46
Sgeo left
06:54
stackspace left
07:52
Aedil left
|
|||
xinming | ab5tract: thanks for the #whateverable note | 08:50 | |
08:57
sena_kun joined
09:36
Aedil joined
|
|||
lizmat | tbrowder: updates on raku.land can be delayed up to several hours due to a bug in the harvesting logic of raku.land, which causes a harvest to fail if one of the servers interrogated answers with a 403 | 09:59 | |
this is a known issue | |||
the module *was* zef installable immediately though, and the REA harvester also indexed it on the next hourly run | 10:00 | ||
11:25
Aedil left
11:26
Aedil joined
11:27
Aedil left
11:28
Aedil joined
11:32
Aedil left
11:33
Aedil joined
|
|||
lizmat | and yet another Rakudo Weekly News hits the Net: rakudoweekly.blog/2024/12/23/2024-...-the-dots/ | 11:57 | |
guifa | m: say sprintf: '%d h%d m%d s', 5,5,5 | 13:20 | |
camelia | ===SORRY!=== Error while compiling <tmp> Calling sprintf() will never work with signature of the proto ($, |) at <tmp>:1 ------> say <HERE>sprintf: '%d h%d m%d s', 5,5,5 |
||
lizmat | m: say sprintf '%d h%d m%d s', 5,5,5 | 13:29 | |
camelia | 5 h5 m5 s | ||
lizmat | guifa: why the colon? | ||
guifa | oh duh | ||
timo | say sprintf: is equivalent to sprintf.say: blah, right? | ||
indirect object notation if i'm not mistaken | 13:30 | ||
but a little surprised that it invokes sprintf with no arguments there. i don't think this syntax is meant to be used like that though? | |||
guifa | timo: no not meant to be used that way, that's just me being an idiot :) | 13:33 | |
timo | i really really rarely ever use that notation in the first place | 13:34 | |
guifa | ah I use it quite a bit | ||
guifa hateses the parenthesesss | |||
lizmat | I usually use it with blocks | 13:35 | |
@a.map: { | |||
... | |||
} | |||
saves on a ; as well then | |||
guifa | I also use it inside of parentheses | ||
@foo.map(*.substr: 0, 1).join is cleaner to me that @foo.map(*.substr(0,1)).join | 13:36 | ||
timo | well, @a.map: isn't indirect object notation | 13:38 | |
that would be map @a: ... | |||
lizmat | right, that was more about using the colon :-) | 13:49 | |
timo | yeah i use the colon for method calls regularly | ||
guifa | oh you were meaning just for indirect. I use it occasionally | 13:50 | |
less so though because most syntax highlighters don't get it | |||
guifa testing out his mDNS-based service discovery module | 14:53 | ||
What am I doing wrong? I can only find like one thing when I'm searching | |||
oh | |||
that's it | |||
99% of devices aren't followings tandard and responding to a "what's out there" query lol | |||
ab5tract | Probably a decent move from a security standpoint… but also a bit self-defeating in terms of the intent of the mDNS protocol :) | 15:26 | |
guifa | oh hmmm actually inspecting via wireshark, maybe I need to double check my moarvm stuff --- it seems i thought I'm sending fpm 5353 but its a randomly assigned port which can be ignored | 15:30 | |
aaaaah I think I see the issue. When we use IO::Socket::Async.udp(...) doesn't let you choose the outgoing port number | 15:38 | ||
if you want to, you need to use bind-udp, which in the docs is listed as just for listening (but can be used for sending as well) | 15:40 | ||
antononcube | If I import JSON file that has new lines (in Raku) I get the message: > Missing serialize REPR function for REPR VMException (BOOTException) | 16:10 | |
It seems to happen with both "JSON::Tiny" and "JSON::Fast". | 16:11 | ||
Since these a certain configuration files, I can control / massage the imported content. But it is inconvenient. | 16:25 | ||
lizmat | antononcube if you could create a golf, please make an issue for it | 16:39 | |
exceptions should just be runtime, they should not be serialized | |||
antononcube | Ok. That happens in INIT phaser in "Jupyter::Chatbook". (Meaning, the code I observer this behavior with is somewhat complicated.) But it is interesting that that problem can be "fixed" by just manipulating the JSON file. | 16:44 | |
So, hopefully, it is simple to narrow down to (much) simpler code. | |||
lizmat | dinner& | ||
timo | ah, we should really figure something out for outputting what's in the exception when it ends up in a serialization context by accident | 17:34 | |
@antononcube, how can i get a little patch of moarvm's C sources to you so you can test if it works with your code? | 17:52 | ||
can't easily trigger the exception myself right now | 18:17 | ||
18:53
Tirifto_ joined
18:58
Tirifto left
|
|||
timo | @antononcube, i have a branch called serialize_vmexception_prints_its_message_and_backtrace which should give a more helpful error message for your issue. can you build moar from source? | 19:01 | |
antononcube | @timo I can try these after 4-5 hours. | 19:03 | |
19:28
bisectable6 left
19:32
bisectable6 joined
|
|||
jdv | ab5tract: you really do java a lot? | 19:49 | |
antononcube | No, little-java, much-kotlin. | 19:55 | |
(At least that is what @ab5tract stated in his Raku Advent 2024 post.) | |||
20:01
Aedil left
20:59
xinming left
|
|||
ab5tract | I do a lot of Java at work | 21:00 | |
antononcube | It is an interesting question do LLMs know Java better Kotlin. | 21:05 | |
Or the other way around, of course. | 21:06 | ||
ab5tract | jdv: why do you ask? | 21:08 | |
21:08
xinming joined
|
|||
jdv | ab5tract: just curious. i don't know that many people who do. | 21:24 | |
ab5tract | Fair enough! It’s an interesting language to be honest, it’s possible to be relatively concise (relative to other Java code, that is) | 22:15 | |
However, I doubt I would ever write a line of it without being paid to do so | 22:17 | ||
s/a/another/ | |||
22:49
Sgeo joined
22:52
cm_ joined
22:53
cm left,
cm_ is now known as cm
22:58
Sgeo left
22:59
Sgeo joined
23:13
sena_kun left
|
|||
guifa | what's the best way to do an enum that you don't want to flood the name space? | 23:37 | |
like that has to be references in full as Foo::A, Foo::B but still lets you say that you want something typed as Foo? | 23:38 | ||
but such that A and B aren't valid constants? I guess just making the enum in a packet and exporting only the top level name? | |||
lizmat | m: my constant A = do { my enum FOO <a b c>; FOO }; dd A; dd A::a; dd a | 23:40 | |
camelia | ===SORRY!=== Error while compiling <tmp> Undeclared routine: a used at line 1 |
||
lizmat | m: my constant A = do { my enum FOO <a b c>; FOO }; dd A; dd A::a | 23:41 | |
camelia | FOO FOO::a |
||
lizmat | guifa: ^^ | ||
guifa | ha that's basically I guess what that exporting would do but without needing a separate package | 23:42 | |
lizmat | yup | ||
guifa | too many overlapping enum names when dealing with DNS | 23:44 | |
*ahem* 'standard' |