Newest at the top
| 2026-04-20 11:45:38 +0000 | Eoco | (~ian@128.101.131.218) (Ping timeout: 252 seconds) |
| 2026-04-20 11:44:41 +0000 | weary-traveler | (~user@user/user363627) user363627 |
| 2026-04-20 11:35:03 +0000 | jreicher | (~joelr@user/jreicher) jreicher |
| 2026-04-20 11:34:09 +0000 | jreicher | (~joelr@user/jreicher) (Quit: brb) |
| 2026-04-20 11:32:15 +0000 | gawen_ | (~gawen@user/gawen) (Ping timeout: 245 seconds) |
| 2026-04-20 11:31:48 +0000 | gawen | (~gawen@user/gawen) gawen |
| 2026-04-20 11:29:36 +0000 | jreicher | (~joelr@user/jreicher) jreicher |
| 2026-04-20 11:28:41 +0000 | jreicher | (~joelr@user/jreicher) (Quit: ERC 5.6.0.30.1 (IRC client for GNU Emacs 30.2)) |
| 2026-04-20 11:24:12 +0000 | tremon | (~tremon@83.80.159.219) tremon |
| 2026-04-20 11:21:01 +0000 | jreicher | (~joelr@user/jreicher) jreicher |
| 2026-04-20 11:19:19 +0000 | jreicher | (~joelr@user/jreicher) (Quit: brb) |
| 2026-04-20 11:16:48 +0000 | xff0x | (~xff0x@2405:6580:b080:900:e1c6:2577:bdda:cb20) |
| 2026-04-20 11:08:35 +0000 | oats | (~oats@user/oats) oats |
| 2026-04-20 11:08:20 +0000 | oats | (~oats@user/oats) (Read error: Connection reset by peer) |
| 2026-04-20 11:04:00 +0000 | <Freakie> | does anyone have suggestions for profiling compact regions? |
| 2026-04-20 11:03:12 +0000 | Freakie | (~Freakie@185.45.22.133) |
| 2026-04-20 11:02:45 +0000 | archking | (~archking@2404:7a83:23e1:9700:9c9e:3aff:fe7a:ed82) (Ping timeout: 246 seconds) |
| 2026-04-20 10:55:28 +0000 | archking | (~archking@2404:7a83:23e1:9700:9c9e:3aff:fe7a:ed82) |
| 2026-04-20 10:54:40 +0000 | divlamir_ | divlamir |
| 2026-04-20 10:54:06 +0000 | divlamir | (~divlamir@user/divlamir) (Ping timeout: 244 seconds) |
| 2026-04-20 10:53:49 +0000 | divlamir_ | (~divlamir@user/divlamir) divlamir |
| 2026-04-20 10:53:22 +0000 | <[exa]> | distinguished |
| 2026-04-20 10:53:20 +0000 | <[exa]> | ...I'm writing a network app, each single thing has to manage like 10 different timeouts. I don't want to completely rely on green threads (instead I'd love to have actual event handlers etc.), so I'd have once somewhat central place where all timeouts and events would get processed and dispatched. Now, scheduled alarms to time-outs are the same "type" of event and I'd love to have them somehow |
| 2026-04-20 10:51:50 +0000 | <[exa]> | is there some nice way to have type-level marks on various events that come to a program? I |
| 2026-04-20 10:45:29 +0000 | divlamir_ | divlamir |
| 2026-04-20 10:45:15 +0000 | divlamir | (~divlamir@user/divlamir) (Ping timeout: 265 seconds) |
| 2026-04-20 10:43:38 +0000 | divlamir_ | (~divlamir@user/divlamir) divlamir |
| 2026-04-20 10:41:24 +0000 | archking | (~archking@2404:7a83:23e1:9700:34ce:6eff:fea6:7b59) (Ping timeout: 246 seconds) |
| 2026-04-20 10:34:12 +0000 | archking | (~archking@2404:7a83:23e1:9700:34ce:6eff:fea6:7b59) |
| 2026-04-20 10:32:24 +0000 | CloneOfN- | (~CloneOfNo@user/CloneOfNone) (Ping timeout: 244 seconds) |
| 2026-04-20 10:31:13 +0000 | CloneOfNone | (~CloneOfNo@user/CloneOfNone) CloneOfNone |
| 2026-04-20 10:23:48 +0000 | CiaoSen | (~Jura@p549cbfb1.dip0.t-ipconnect.de) CiaoSen |
| 2026-04-20 10:23:19 +0000 | <probie> | gentauro: my intuition says you that you're probably doing the "wrong thing" if you want this function for lists (arrays, vectors, bytestrings and possibly text it makes some sense for) |
| 2026-04-20 10:22:22 +0000 | archking | (~archking@2404:7a83:23e1:9700:a812:17ff:fe6e:b27) (Ping timeout: 276 seconds) |
| 2026-04-20 10:21:38 +0000 | xff0x | (~xff0x@fsb6a9491c.tkyc517.ap.nuro.jp) (Ping timeout: 248 seconds) |
| 2026-04-20 10:16:59 +0000 | fp1 | (~Thunderbi@wireless-86-50-141-149.open.aalto.fi) (Ping timeout: 245 seconds) |
| 2026-04-20 10:14:16 +0000 | archking | (~archking@2404:7a83:23e1:9700:a812:17ff:fe6e:b27) |
| 2026-04-20 10:01:25 +0000 | archking | (~archking@2404:7a83:23e1:9700:ec83:3ff:fe20:5a7e) (Ping timeout: 245 seconds) |
| 2026-04-20 09:54:05 +0000 | archking | (~archking@2404:7a83:23e1:9700:ec83:3ff:fe20:5a7e) |
| 2026-04-20 09:53:36 +0000 | divlamir | (~divlamir@user/divlamir) divlamir |
| 2026-04-20 09:53:14 +0000 | acidjnk_new | (~acidjnk@p200300d6e700e528fc1f390accc80343.dip0.t-ipconnect.de) (Ping timeout: 245 seconds) |
| 2026-04-20 09:50:35 +0000 | dpk | (~dpk@jains.nonceword.org) (Ping timeout: 245 seconds) |
| 2026-04-20 09:50:33 +0000 | acidjnk_new3 | (~acidjnk@p200300d6e700e5655d8f1f6a4acafa55.dip0.t-ipconnect.de) acidjnk |
| 2026-04-20 09:44:33 +0000 | CiaoSen | (~Jura@p549cbfb1.dip0.t-ipconnect.de) (Ping timeout: 255 seconds) |
| 2026-04-20 09:43:37 +0000 | divlamir | (~divlamir@user/divlamir) (Ping timeout: 248 seconds) |
| 2026-04-20 09:40:09 +0000 | archking | (~archking@2404:7a83:23e1:9700:1cc6:bff:fe8c:df07) (Ping timeout: 246 seconds) |
| 2026-04-20 09:33:02 +0000 | archking | (~archking@2404:7a83:23e1:9700:1cc6:bff:fe8c:df07) |
| 2026-04-20 09:27:33 +0000 | fp1 | (~Thunderbi@wireless-86-50-141-149.open.aalto.fi) fp |
| 2026-04-20 09:19:14 +0000 | archking | (~archking@2404:7a83:23e1:9700:4417:bff:fe77:7fb8) (Ping timeout: 248 seconds) |
| 2026-04-20 09:14:38 +0000 | sa | (sid1055@id-1055.tinside.irccloud.com) sa |