2026/02/04

Newest at the top

2026-02-04 11:38:57 +0100trickard_trickard
2026-02-04 11:37:18 +0100vanishingideal(~vanishing@user/vanishingideal) vanishingideal
2026-02-04 11:32:04 +0100AlexNoo_AlexNoo
2026-02-04 11:31:43 +0100qqq(~qqq@185.54.21.178) (Ping timeout: 244 seconds)
2026-02-04 11:25:29 +0100 <[exa]> gentauro: given the amount of "complete" code they have on githubs I'd say this might be a case for poc||gtfo
2026-02-04 11:22:05 +0100 <gentauro> I mean, all the things that he mentions are "extremely hard" to do on its own.
2026-02-04 11:21:32 +0100 <gentauro> [exa]: if you search for "// F* specification for verified memory operation" it seems that he also will add somekind of `liquid F#/F*` support? https://speakez.tech/blog/doubling-down/
2026-02-04 11:14:25 +0100housemate(~housemate@202.7.248.67) (Quit: https://ineedsomeacidtocalmmedown.space/)
2026-02-04 11:07:49 +0100AlexNoo(~AlexNoo@85.174.181.199) (Ping timeout: 260 seconds)
2026-02-04 11:05:18 +0100AlexNoo_(~AlexNoo@85.174.181.199)
2026-02-04 11:05:16 +0100AlexZenon(~alzenon@85.174.181.199)
2026-02-04 11:04:54 +0100AlexNoo__(~AlexNoo@85.174.181.199) (Ping timeout: 260 seconds)
2026-02-04 11:04:19 +0100AlexNoo_(~AlexNoo@85.174.181.199) (Ping timeout: 260 seconds)
2026-02-04 11:03:33 +0100AlexNoo(~AlexNoo@85.174.181.199)
2026-02-04 11:03:07 +0100AlexNoo(~AlexNoo@178.34.150.239) (Ping timeout: 246 seconds)
2026-02-04 11:01:49 +0100AlexZenon(~alzenon@178.34.150.239) (Ping timeout: 264 seconds)
2026-02-04 11:00:25 +0100AlexNoo__(~AlexNoo@85.174.181.199)
2026-02-04 10:59:39 +0100AlexNoo_(~AlexNoo@85.174.181.199)
2026-02-04 10:51:40 +0100fp(~Thunderbi@wireless-86-50-140-153.open.aalto.fi) (Ping timeout: 255 seconds)
2026-02-04 10:37:02 +0100weary-traveler(~user@user/user363627) user363627
2026-02-04 10:32:34 +0100trickard_(~trickard@cpe-61-98-47-163.wireline.com.au)
2026-02-04 10:32:04 +0100fp(~Thunderbi@wireless-86-50-140-153.open.aalto.fi) fp
2026-02-04 10:31:53 +0100trickard_(~trickard@cpe-61-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2026-02-04 10:29:45 +0100qqq(~qqq@185.54.21.178)
2026-02-04 10:21:56 +0100trickard_(~trickard@cpe-61-98-47-163.wireline.com.au)
2026-02-04 10:21:43 +0100trickard_(~trickard@cpe-61-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2026-02-04 10:20:01 +0100housemate(~housemate@202.7.248.67) housemate
2026-02-04 10:19:01 +0100ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 246 seconds)
2026-02-04 10:18:26 +0100lucabtz(~lucabtz@user/lucabtz) lucabtz
2026-02-04 10:15:19 +0100xff0x(~xff0x@fsb6a9491c.tkyc517.ap.nuro.jp) (Ping timeout: 264 seconds)
2026-02-04 10:09:34 +0100fp(~Thunderbi@wireless-86-50-140-153.open.aalto.fi) (Ping timeout: 246 seconds)
2026-02-04 10:06:07 +0100trickard_(~trickard@cpe-61-98-47-163.wireline.com.au)
2026-02-04 10:05:53 +0100trickard_(~trickard@cpe-61-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2026-02-04 10:05:27 +0100fp(~Thunderbi@wireless-86-50-140-153.open.aalto.fi) fp
2026-02-04 10:02:21 +0100ljdarj(~Thunderbi@user/ljdarj) ljdarj
2026-02-04 09:57:29 +0100merijn(~merijn@77.242.116.146) merijn
2026-02-04 09:53:05 +0100housemate(~housemate@202.7.248.67) (Quit: https://ineedsomeacidtocalmmedown.space/)
2026-02-04 09:52:28 +0100prdak(~Thunderbi@user/prdak) (Quit: prdak)
2026-02-04 09:40:42 +0100chele(~chele@user/chele) chele
2026-02-04 09:40:29 +0100emmanuelux(~em@user/emmanuelux) (Quit: bye)
2026-02-04 09:32:55 +0100xff0x(~xff0x@fsb6a9491c.tkyc517.ap.nuro.jp)
2026-02-04 09:30:36 +0100xff0x(~xff0x@fsb6a9491c.tkyc517.ap.nuro.jp) (Quit: xff0x)
2026-02-04 09:23:36 +0100_JusSx_(~jussx@78.210.76.107)
2026-02-04 09:22:31 +0100_JusSx_(~jussx@78.210.76.107) (Ping timeout: 240 seconds)
2026-02-04 09:22:05 +0100 <[exa]> anyway any ideas welcome. :D
2026-02-04 09:21:52 +0100 <[exa]> (duck effect: I realized I might just place a limit on the queue size instead of the thread count, which would probably also limit the possible amount of stupid work done over the queue)
2026-02-04 09:20:41 +0100 <[exa]> sound very good to me (I'll have to scan it quite often to find new work items, so it might get quite slow)
2026-02-04 09:20:39 +0100 <[exa]> hm I guess better ask about the original problem.. I have a few concurrent helpers for Streaming, and I want to have a parallel unfolding function. Example here: https://paste.tomsmeding.com/y8PLkSYh -- mapMForkNIO works, unfoldStream works, and I'd love to them combined, but I can't see a good data structure that would hold the temporary data for it together. Having a list queue there doesn't
2026-02-04 09:19:16 +0100sord937(~sord937@gateway/tor-sasl/sord937) sord937
2026-02-04 09:17:19 +0100peterbecich(~Thunderbi@71.84.33.135) (Ping timeout: 240 seconds)