| guifa | meh, just going with .foo with %hash<foo> //= Foo.new; I think it's as concise as I'll get | 01:00 | |
|
01:34
lizmat_ left
01:35
lizmat joined
02:04
hulk joined
02:05
kylese left
|
|||
| timo | could make an operator like postfix:<++> that just doesn't increment or anything | 02:12 | |
| guifa | timo: true, but I think my final one is at least recognizable if not quite a pattern | 02:15 | |
| also, I just realized that this mDNS / Zerconf module / project would make a badass talk on concurrency | 02:16 | ||
| I have supplies leading to supplies leading to supplies | |||
| and yet the design is crazy clean | |||
| udp port gives a supply, packets are processed by the mDNS server and records are put into a set of supplies based on types. the zeroconf module is subscribed to those and makes additional queries as needed to scope out the landscape and, based on what it finds, emits records onto yet another supply | 02:18 | ||
| and the end user just does my $zc = Zeroconf.new; $zc.service-notification('_printer._tcp.local').tap: -> { ... } | 02:19 | ||
|
03:15
hulk left,
kylese joined
|
|||
| ab5tract | guifa: snazzy! | 03:21 | |
| guifa | I mean, I'm sure if I made it a monolith in C it'd be about a gazillion times more efficient, but so far, it seems more than fast enough for mDNS | 03:57 | |
|
03:59
Sgeo left
04:03
Sgeo joined
04:35
Aedil joined
|
|||
| aruniecrisps | @ab5stract tried doing that, doesn't seem to be doing anything it looks like | 05:05 | |
| ab5tract | Boo :( | 05:33 | |
| Next best thing might be to nuke the whole dependency | 05:34 | ||
|
07:22
Xliff joined
|
|||
| Xliff | Can someone explain to me the arguments for the following call? - go_path_pie_wedge (GOPath *path, double cx, double cy, double rx, double ry, double th0, double th1) | 07:23 | |
| I'm fine with the first 2, but the rest of them are confusing. | |||
| The first 3 rather. I'm trying to write bindings for this in raku. | |||
| I think I lost a brain cell or two within the last 5000 lines of Gnumeric/GOffice | 07:24 | ||