Newest at the top
2025-03-11 10:03:05 +0100 | infinity0 | (~infinity0@pwned.gg) infinity0 |
2025-03-11 10:02:03 +0100 | merijn | (~merijn@77.242.116.146) (Ping timeout: 245 seconds) |
2025-03-11 09:58:40 +0100 | chele | (~chele@user/chele) chele |
2025-03-11 09:54:10 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 265 seconds) |
2025-03-11 09:53:23 +0100 | merijn | (~merijn@77.242.116.146) merijn |
2025-03-11 09:52:37 +0100 | infinity0 | (~infinity0@pwned.gg) (Ping timeout: 248 seconds) |
2025-03-11 09:49:31 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
2025-03-11 09:42:51 +0100 | sord937 | (~sord937@gateway/tor-sasl/sord937) sord937 |
2025-03-11 09:42:31 +0100 | sord937 | (~sord937@gateway/tor-sasl/sord937) (Remote host closed the connection) |
2025-03-11 09:41:04 +0100 | alp | (~alp@2001:861:8ca0:4940:10bd:451c:fec0:8bc1) |
2025-03-11 09:41:01 +0100 | sarna | (~sarna@d168-237.icpnet.pl) sarna |
2025-03-11 09:39:20 +0100 | <tomsmeding> | Writing in programming language order and then adding markers to rearrange it into prose sounds like a very good way to turn yourself mad :) |
2025-03-11 09:38:15 +0100 | <tomsmeding> | I have not only not done literate programming for a long time, I have _never_ done it yet. So partly I'm talking from void here |
2025-03-11 09:37:30 +0100 | <tomsmeding> | A programming language should optimise for maintainability, understandability given that you already get the structure of the code (which should be explained by a comment, alternative documentation, etc.) |
2025-03-11 09:37:04 +0100 | <tomsmeding> | I guess my point is that lecture notes are not what a programming language should optimise for |
2025-03-11 09:36:52 +0100 | <tomsmeding> | monochrom: Aside asynchronous communication over IRC is not particularly practical. :P |
2025-03-11 09:30:19 +0100 | <dminuoso> | It avoids memory issues by keeping potentially large queues on disk, while automatic linux buffer memories should give near in-memory performance on average |
2025-03-11 09:29:40 +0100 | acidjnk_new | (~acidjnk@p200300d6e7283f28c0a9d5fbe208cdcd.dip0.t-ipconnect.de) |
2025-03-11 09:29:24 +0100 | <dminuoso> | Maybe instead of simulating a file API, I should just use files. |
2025-03-11 09:28:14 +0100 | Smiles | (uid551636@id-551636.lymington.irccloud.com) Smiles |
2025-03-11 09:27:57 +0100 | sarna | (~sarna@d168-237.icpnet.pl) (Ping timeout: 276 seconds) |
2025-03-11 09:07:55 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 244 seconds) |
2025-03-11 09:04:53 +0100 | ft | (~ft@p508db291.dip0.t-ipconnect.de) (Quit: leaving) |
2025-03-11 09:04:52 +0100 | sord937 | (~sord937@gateway/tor-sasl/sord937) sord937 |
2025-03-11 09:03:46 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
2025-03-11 08:56:22 +0100 | machinedgod | (~machinedg@d108-173-18-100.abhsia.telus.net) machinedgod |
2025-03-11 08:51:48 +0100 | tzh | (~tzh@c-76-115-131-146.hsd1.or.comcast.net) (Quit: zzz) |
2025-03-11 08:51:31 +0100 | izzyfalco | (~jake_pers@user/izzyfalco) izzyfalco |
2025-03-11 08:47:06 +0100 | <Leary> | (wanting to do so suggests you might actually want a denser representation; perhaps an exponentially-growing `Vector` in a `TVar` with some cursor tracking state on each side) |
2025-03-11 08:45:23 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds) |
2025-03-11 08:41:56 +0100 | <Leary> | dminuoso: If you need new clients to see old elements, it will have to be `newTChan` and `cloneTChan` instead, it's just that holding onto everything a channel has ever seen is usually a bad idea. |
2025-03-11 08:40:49 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
2025-03-11 08:40:03 +0100 | <dminuoso> | Leary: Anyway, thanks for the confirmation. |
2025-03-11 08:39:48 +0100 | <dminuoso> | Since consumers may connect after some clients have read them |
2025-03-11 08:39:36 +0100 | <dminuoso> | That is, I *want* items to stay around even if they have been read |
2025-03-11 08:39:15 +0100 | <dminuoso> | " By using newBroadcastTChan to create the broadcast channel, items can be garbage collected after clients have seen them." reads as if I have to use newTChan rather than newBroadcastTChan |
2025-03-11 08:33:51 +0100 | <Leary> | dminuoso: Yes, that's what `newBroadcastTChan` and `dupTChan` are for. |
2025-03-11 08:31:12 +0100 | <dminuoso> | Or mm. Perhaps a writer TChan + cloned reader TChan is all I need |
2025-03-11 08:30:32 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 272 seconds) |
2025-03-11 08:29:40 +0100 | <dminuoso> | Is there a type of STM multi-consumer queue, where consumers can be connected after the queue was created, and each consumer can consume at their own pace? I'm roughly trying to mimic a file API here. |
2025-03-11 08:25:27 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
2025-03-11 08:23:35 +0100 | CiaoSen | (~Jura@2a02:8071:64e1:7180:4e50:ddff:fe9b:8922) CiaoSen |
2025-03-11 08:21:54 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 246 seconds) |
2025-03-11 08:17:42 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
2025-03-11 08:15:30 +0100 | ash3en | (~Thunderbi@89.56.182.235) ash3en |
2025-03-11 08:14:57 +0100 | ash3en | (~Thunderbi@89.56.182.235) (Remote host closed the connection) |
2025-03-11 08:14:36 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds) |
2025-03-11 08:13:34 +0100 | Lord_of_Life_ | Lord_of_Life |
2025-03-11 08:13:26 +0100 | Lord_of_Life | (~Lord@user/lord-of-life/x-2819915) (Ping timeout: 272 seconds) |
2025-03-11 08:12:13 +0100 | Lord_of_Life_ | (~Lord@user/lord-of-life/x-2819915) Lord_of_Life |