Newest at the top
| 2025-03-19 06:37:54 +0100 | hattckory | (~hattckory@bras-base-toroon4524w-grc-47-184-146-98-182.dsl.bell.ca) (Ping timeout: 248 seconds) |
| 2025-03-19 06:36:20 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-03-19 06:34:19 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds) |
| 2025-03-19 06:33:39 +0100 | hattckory | (~hattckory@bras-base-toroon4524w-grc-47-184-146-98-182.dsl.bell.ca) |
| 2025-03-19 06:27:20 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-03-19 06:23:30 +0100 | Googulator3 | (~Googulato@80-95-93-233.pool.digikabel.hu) |
| 2025-03-19 06:23:13 +0100 | Googulator3 | (~Googulato@80-95-93-233.pool.digikabel.hu) (Client Quit) |
| 2025-03-19 06:22:28 +0100 | Googulator68 | (~Googulato@2a01-036d-0106-0ae4-b88c-ff83-9891-e272.pool6.digikabel.hu) (Quit: Client closed) |
| 2025-03-19 06:21:21 +0100 | Googulator3 | (~Googulato@80-95-93-233.pool.digikabel.hu) |
| 2025-03-19 06:19:35 +0100 | tavare | (~tavare@user/tavare) (Remote host closed the connection) |
| 2025-03-19 06:18:22 +0100 | kh0d | (~kh0d@212.200.247.168) (Ping timeout: 265 seconds) |
| 2025-03-19 06:18:15 +0100 | fantom | (~fantom@2.219.56.221) |
| 2025-03-19 06:18:03 +0100 | fantom | (~fantom@2.219.56.221) (Ping timeout: 244 seconds) |
| 2025-03-19 06:16:37 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds) |
| 2025-03-19 06:15:35 +0100 | tavare | (~tavare@user/tavare) tavare |
| 2025-03-19 06:13:36 +0100 | kh0d | (~kh0d@212.200.247.168) kh0d |
| 2025-03-19 06:13:11 +0100 | fantom | (~fantom@2.219.56.221) |
| 2025-03-19 06:11:33 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-03-19 06:06:28 +0100 | tavare | (~tavare@user/tavare) (Ping timeout: 272 seconds) |
| 2025-03-19 06:01:00 +0100 | kh0d | (~kh0d@212.200.247.168) (Ping timeout: 252 seconds) |
| 2025-03-19 06:00:31 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2025-03-19 05:56:22 +0100 | kh0d | (~kh0d@212.200.247.168) |
| 2025-03-19 05:55:46 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-03-19 05:55:30 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 252 seconds) |
| 2025-03-19 05:53:57 +0100 | <jackdk> | Huh, I found a 3.5yo PR of mine against cereal still open, perhaps that's why I switched to `binary`. |
| 2025-03-19 05:52:34 +0100 | hattckory | (~hattckory@184.146.98.182) (Ping timeout: 260 seconds) |
| 2025-03-19 05:52:27 +0100 | michalz | (~michalz@185.246.207.193) |
| 2025-03-19 05:52:13 +0100 | a_fantom | (~fantom@2.219.56.221) (Ping timeout: 244 seconds) |
| 2025-03-19 05:51:17 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-03-19 05:49:19 +0100 | <jackdk> | I wonder if https://hackage.haskell.org/package/attoparsec-binary-0.2 still works? Some very ambitious bounds and a 2012 upload date |
| 2025-03-19 05:48:25 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2025-03-19 05:47:47 +0100 | <Axman6> | A big thing that was missing was parsing integers of fixed sizes and endianesses, which I'm sure surprises me every timeI try to use it for binary parsing |
| 2025-03-19 05:46:56 +0100 | <jackdk> | I usually consider attoparsec suitable for binary formats. Last time I did binary parsing I used package `binary` over `cereal` but I couldn't tell you why. Maybe the more recent upload date? |
| 2025-03-19 05:44:59 +0100 | aforemny_ | (~aforemny@2001:9e8:6cc7:6b00:b975:f736:215a:5f1e) (Ping timeout: 260 seconds) |
| 2025-03-19 05:44:15 +0100 | aforemny | (~aforemny@2001:9e8:6ce6:a700:9c3f:a849:8d9b:359a) aforemny |
| 2025-03-19 05:43:49 +0100 | Unicorn_Princess | (~Unicorn_P@user/Unicorn-Princess/x-3540542) (Remote host closed the connection) |
| 2025-03-19 05:43:41 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-03-19 05:43:33 +0100 | <Axman6> | bloody bogans |
| 2025-03-19 05:43:12 +0100 | <jackdk> | Axman6: I think youz'll find that it's spelt "yooz" |
| 2025-03-19 05:41:39 +0100 | kh0d | (~kh0d@212.200.247.168) (Ping timeout: 260 seconds) |
| 2025-03-19 05:40:58 +0100 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich |
| 2025-03-19 05:39:15 +0100 | Feuermagier | (~Feuermagi@user/feuermagier) Feuermagier |
| 2025-03-19 05:36:06 +0100 | kh0d | (~kh0d@212.200.247.168) kh0d |
| 2025-03-19 05:32:40 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2025-03-19 05:28:35 +0100 | <Axman6> | (I'm Australian, youse is an important word in our culture) |
| 2025-03-19 05:28:17 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-03-19 05:27:24 +0100 | <Axman6> | Which parsing library would youse use for parsing binary protocols today? I would usually look at attoparsec, but it's definitely more aimed at textual parsing. Binary is possibly ok, but I'm wondering if there's any other options these days |
| 2025-03-19 05:23:17 +0100 | kh0d_ | (~kh0d@212.200.247.168) (Ping timeout: 248 seconds) |
| 2025-03-19 05:17:53 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 268 seconds) |
| 2025-03-19 05:13:27 +0100 | statusbot | (~statusbot@ec2-34-198-122-184.compute-1.amazonaws.com) statusbot |