Newest at the top
| 2026-02-25 03:33:47 +0100 | mstruebing | (~mstruebin@ns343649.ip-188-165-193.eu) |
| 2026-02-25 03:33:39 +0100 | mstruebing | (~mstruebin@ns343649.ip-188-165-193.eu) (Server closed connection) |
| 2026-02-25 03:29:45 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds) |
| 2026-02-25 03:25:12 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-25 03:14:03 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 246 seconds) |
| 2026-02-25 03:09:50 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-25 03:08:24 +0100 | Googulator | (~Googulato@2a01-036d-0106-499d-1c5a-0e4b-5795-d7e3.pool6.digikabel.hu) |
| 2026-02-25 03:08:08 +0100 | Googulator | (~Googulato@2a01-036d-0106-499d-1c5a-0e4b-5795-d7e3.pool6.digikabel.hu) (Quit: Client closed) |
| 2026-02-25 03:01:32 +0100 | rainbyte_ | (~rainbyte@186.22.19.214) (Quit: rainbyte_) |
| 2026-02-25 03:01:31 +0100 | uli-fem | ulipink |
| 2026-02-25 03:01:23 +0100 | uli-fem | (~uli-fem@user/uli-fem) uli-fem |
| 2026-02-25 03:01:23 +0100 | uli-fem | (~uli-fem@118.210.1.123) (Changing host) |
| 2026-02-25 02:59:57 +0100 | uli-fem | (~uli-fem@118.210.1.123) |
| 2026-02-25 02:58:55 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds) |
| 2026-02-25 02:56:23 +0100 | Vizious | (~bes@user/Vizious) (Quit: WeeChat 4.8.1) |
| 2026-02-25 02:54:28 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-25 02:52:44 +0100 | wickedjargon | (~user@2605:8d80:5430:8458:d04:837d:bf6b:e6b3) wickedjargon |
| 2026-02-25 02:43:57 +0100 | Tuplanolla | (~Tuplanoll@88-114-89-88.elisa-laajakaista.fi) (Ping timeout: 246 seconds) |
| 2026-02-25 02:43:30 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds) |
| 2026-02-25 02:40:15 +0100 | Sgeo | (~Sgeo@user/sgeo) Sgeo |
| 2026-02-25 02:39:06 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-25 02:27:49 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds) |
| 2026-02-25 02:24:27 +0100 | Sgeo | (~Sgeo@user/sgeo) (Read error: Connection reset by peer) |
| 2026-02-25 02:21:05 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-25 02:10:10 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds) |
| 2026-02-25 02:05:43 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-25 01:55:03 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 272 seconds) |
| 2026-02-25 01:50:21 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-25 01:46:17 +0100 | xff0x | (~xff0x@ai083101.d.east.v6connect.net) (Ping timeout: 265 seconds) |
| 2026-02-25 01:41:14 +0100 | lally | (sid388228@id-388228.uxbridge.irccloud.com) lally |
| 2026-02-25 01:40:59 +0100 | lally | (sid388228@id-388228.uxbridge.irccloud.com) (Server closed connection) |
| 2026-02-25 01:39:50 +0100 | tritlo | (sid58727@id-58727.hampstead.irccloud.com) |
| 2026-02-25 01:39:39 +0100 | tritlo | (sid58727@id-58727.hampstead.irccloud.com) (Server closed connection) |
| 2026-02-25 01:39:20 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds) |
| 2026-02-25 01:34:58 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-25 01:34:42 +0100 | <EvanR> | yes constructing an infinite value seems kind of vague operationally, so agree that makes it hard to predict the memory usage pattern |
| 2026-02-25 01:29:43 +0100 | robobub | (uid248673@id-248673.uxbridge.irccloud.com) robobub |
| 2026-02-25 01:26:39 +0100 | <int-e> | EvanR: The main reason I think of it that way is that it becomes harder to ensure that you expand exactly the parts of the tree that you need and you also release them to the garbage collector once you're done with them. |
| 2026-02-25 01:23:55 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds) |
| 2026-02-25 01:22:11 +0100 | <int-e> | EvanR: But yes, I may be abusing terminology a bit here. |
| 2026-02-25 01:20:57 +0100 | <int-e> | EvanR: well, no; laziness will still be a factor. |
| 2026-02-25 01:20:33 +0100 | <EvanR> | materialize = have the normal form all in memory ? |
| 2026-02-25 01:19:36 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-25 01:19:04 +0100 | <Comstar> | int-e, heard, thanks! |
| 2026-02-25 01:16:27 +0100 | peterbecich | (~Thunderbi@71.84.33.135) (Ping timeout: 246 seconds) |
| 2026-02-25 01:11:43 +0100 | GdeVolpiano | (~GdeVolpia@user/GdeVolpiano) GdeVolpiano |
| 2026-02-25 01:11:08 +0100 | <EvanR> | lantti, going through String is probably not great, and then i/o on the Char is doing unicode stuff, and ... |
| 2026-02-25 01:08:45 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 246 seconds) |
| 2026-02-25 01:07:54 +0100 | <int-e> | I mean constructing a (potentially infinite) value of type `Tree S` where `data Tree s = Node s [Tree s]` from a root :: S and a branching function as above. |
| 2026-02-25 01:05:55 +0100 | <Comstar> | what's materializing the tree mean? |