Newest at the top
| 2025-12-26 18:17:52 +0100 | synchromesh | (~john@2406:5a00:2412:2c00:68ff:586d:59bf:bb1) synchromesh |
| 2025-12-26 18:16:43 +0100 | <ncf> | oh never mind, i misread |
| 2025-12-26 18:16:33 +0100 | marinelli | (~weechat@gateway/tor-sasl/marinelli) marinelli |
| 2025-12-26 18:16:25 +0100 | synchromesh | (~john@2406:5a00:2412:2c00:68ff:586d:59bf:bb1) (Read error: Connection reset by peer) |
| 2025-12-26 18:15:31 +0100 | <ncf> | ? |
| 2025-12-26 18:14:14 +0100 | <haskellbridge> | <Liamzee> I thought of it more like, actions doing so |
| 2025-12-26 18:14:04 +0100 | <haskellbridge> | <Liamzee> i just never thought about it in the sense of having pure functions evaluate through unsafeInterleaveIO |
| 2025-12-26 18:13:23 +0100 | <geekosaur> | and why it's `unsafe` |
| 2025-12-26 18:13:17 +0100 | sroso | (~sroso@user/SrOso) SrOso |
| 2025-12-26 18:13:11 +0100 | <geekosaur> | yep, that's exactly the point of it |
| 2025-12-26 18:12:54 +0100 | <haskellbridge> | <Liamzee> but, implicitly, i can have a pure function trigger an effect on its own simply by evaluating a value that causes unsafeInterleaveIO to throw effects |
| 2025-12-26 18:12:42 +0100 | <geekosaur> | yes |
| 2025-12-26 18:11:43 +0100 | <haskellbridge> | <Liamzee> umm, been thinking, doesn't unsafeInterleaveIO violate referential transparency? I guess that's implied by the name! |
| 2025-12-26 18:10:20 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds) |
| 2025-12-26 18:05:34 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-26 17:56:39 +0100 | Digitteknohippie | Digit |
| 2025-12-26 17:56:37 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 246 seconds) |
| 2025-12-26 17:51:40 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-26 17:40:49 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds) |
| 2025-12-26 17:37:59 +0100 | ZLima12 | (~zlima12@user/meow/ZLima12) (Ping timeout: 260 seconds) |
| 2025-12-26 17:37:44 +0100 | ZLima12_ | (~zlima12@user/meow/ZLima12) ZLima12 |
| 2025-12-26 17:36:09 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-26 17:32:10 +0100 | wootehfoot | (~wootehfoo@user/wootehfoot) (Ping timeout: 255 seconds) |
| 2025-12-26 17:24:55 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds) |
| 2025-12-26 17:20:22 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-26 17:09:19 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds) |
| 2025-12-26 17:04:33 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-26 17:03:58 +0100 | Axman6 | (~Axman6@user/axman6) (Remote host closed the connection) |
| 2025-12-26 17:00:32 +0100 | karenw | (~karenw@user/karenw) (Quit: Deep into that darkness peering...) |
| 2025-12-26 16:55:59 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds) |
| 2025-12-26 16:50:55 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-26 16:40:10 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds) |
| 2025-12-26 16:35:09 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-26 16:34:24 +0100 | Sgeo | (~Sgeo@user/sgeo) Sgeo |
| 2025-12-26 16:31:28 +0100 | <[exa]> | yeah, it's ... unpleasantly rigorous |
| 2025-12-26 16:28:23 +0100 | wootehfoot | (~wootehfoo@user/wootehfoot) wootehfoot |
| 2025-12-26 16:23:55 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds) |
| 2025-12-26 16:21:54 +0100 | <Franciman> | hi ncf ! |
| 2025-12-26 16:20:07 +0100 | <Franciman> | they mention this phenomenon in the mailing list that is referred to in the stackoverflow thread |
| 2025-12-26 16:19:32 +0100 | <ncf> | (well, i think there's only one (lawful) monad instance you can write) |
| 2025-12-26 16:19:21 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-26 16:18:33 +0100 | <[exa]> | thanks :) |
| 2025-12-26 16:18:24 +0100 | <[exa]> | ok fair enough |
| 2025-12-26 16:18:20 +0100 | <[exa]> | Franciman ncf oh so it's mainly to force the instance into existence while aligning with how the applicative works |
| 2025-12-26 16:08:35 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds) |
| 2025-12-26 16:06:26 +0100 | karenw | (~karenw@user/karenw) karenw |
| 2025-12-26 16:04:23 +0100 | CiaoSen | (~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) (Ping timeout: 265 seconds) |
| 2025-12-26 16:03:33 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-26 16:01:54 +0100 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) humasect |
| 2025-12-26 16:00:07 +0100 | YoungFrog | (~youngfrog@2a02:a03f:ca07:f900:2fab:8436:f7d2:8c4a) youngfrog |