Newest at the top
| 2025-03-22 23:18:04 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-03-22 23:18:03 +0100 | hattckory | (~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca) |
| 2025-03-22 23:17:29 +0100 | tromp | (~textual@2001:1c00:3487:1b00:e1c2:84b0:caab:9b02) |
| 2025-03-22 23:16:07 +0100 | sabathan | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-03-22 23:14:56 +0100 | tromp | (~textual@2001:1c00:3487:1b00:e1c2:84b0:caab:9b02) (Quit: My iMac has gone to sleep. ZZZzzz…) |
| 2025-03-22 23:07:32 +0100 | sabathan | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Read error: Connection reset by peer) |
| 2025-03-22 23:07:00 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2025-03-22 23:03:46 +0100 | litharge | (litharge@libera/bot/litharge) litharge |
| 2025-03-22 23:00:59 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-03-22 22:50:02 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2025-03-22 22:50:02 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 252 seconds) |
| 2025-03-22 22:48:46 +0100 | Feuermagier | (~Feuermagi@user/feuermagier) Feuermagier |
| 2025-03-22 22:48:15 +0100 | Feuermagier | (~Feuermagi@user/feuermagier) (Quit: Leaving) |
| 2025-03-22 22:46:45 +0100 | michalz | (~michalz@185.246.207.217) (Remote host closed the connection) |
| 2025-03-22 22:45:34 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-03-22 22:45:13 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-03-22 22:44:55 +0100 | dhil | (~dhil@2a0c:b381:52e:3600:848b:16f:d0fd:be16) dhil |
| 2025-03-22 22:38:50 +0100 | olivial | (~benjaminl@user/benjaminl) benjaminl |
| 2025-03-22 22:37:49 +0100 | hattckory | (~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca) (Ping timeout: 260 seconds) |
| 2025-03-22 22:37:35 +0100 | <geekosaur> | well, it can send edits for the immediately preceding message, but for older ones there's no context so it has to resend |
| 2025-03-22 22:37:11 +0100 | olivial | (~benjaminl@user/benjaminl) (Remote host closed the connection) |
| 2025-03-22 22:36:58 +0100 | olivial | (~benjaminl@user/benjaminl) benjaminl |
| 2025-03-22 22:36:45 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2025-03-22 22:36:22 +0100 | olivial | (~benjaminl@user/benjaminl) (Remote host closed the connection) |
| 2025-03-22 22:33:42 +0100 | j1n37 | (~j1n37@user/j1n37) j1n37 |
| 2025-03-22 22:33:28 +0100 | <haskellbridge> | <dmjio> Sorry IRC people |
| 2025-03-22 22:32:44 +0100 | hattckory | (~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca) |
| 2025-03-22 22:32:08 +0100 | Feuermagier | (~Feuermagi@user/feuermagier) Feuermagier |
| 2025-03-22 22:31:34 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-03-22 22:31:22 +0100 | <EvanR> | yeah the bridge repeats the whole message |
| 2025-03-22 22:30:35 +0100 | <haskellbridge> | <dmjio> The thread delay? |
| 2025-03-22 22:30:14 +0100 | j1n37 | (~j1n37@user/j1n37) (Read error: Connection reset by peer) |
| 2025-03-22 22:28:27 +0100 | hattckory | (~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca) (Ping timeout: 276 seconds) |
| 2025-03-22 22:23:28 +0100 | hattckory | (~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca) |
| 2025-03-22 22:21:34 +0100 | <EvanR> | oof that edit caused a blast from the past |
| 2025-03-22 22:21:03 +0100 | <haskellbridge> | <dmjio> I have some nested threads each with its own stack and heap, the threads are bubbling up killThread events. While bubbling I’m trying to invoke a yield so their stacks can get evaluated and these thunks on the heap will get forced before they all get GC’d. What’s happening is that these thunks are never getting forced and just getting GC’d before evaluation. When I do a "threadDelay 0" they do get evaluated |
| 2025-03-22 22:20:48 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2025-03-22 22:15:49 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-03-22 22:12:53 +0100 | <haskellbridge> | <dmjio> I’ll test on threaded GHC to see if yield behaves |
| 2025-03-22 22:11:45 +0100 | dibblego | (~dibblego@haskell/developer/dibblego) dibblego |
| 2025-03-22 22:11:45 +0100 | dibblego | (~dibblego@116-255-1-119.ip4.superloop.au) (Changing host) |
| 2025-03-22 22:11:45 +0100 | dibblego | (~dibblego@116-255-1-119.ip4.superloop.au) |
| 2025-03-22 22:07:03 +0100 | dibblego | (~dibblego@haskell/developer/dibblego) (Ping timeout: 252 seconds) |
| 2025-03-22 22:05:09 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 260 seconds) |
| 2025-03-22 22:04:56 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2025-03-22 22:04:39 +0100 | <haskellbridge> | <dmjio> Yield could mean give me a different set of threads, not a different set of stack frames. It depends what it means. I bet the yield is defined only in terms of multicore |
| 2025-03-22 22:02:07 +0100 | dibblego | (~dibblego@haskell/developer/dibblego) dibblego |
| 2025-03-22 22:02:07 +0100 | dibblego | (~dibblego@116-255-1-119.ip4.superloop.au) (Changing host) |
| 2025-03-22 22:02:07 +0100 | dibblego | (~dibblego@116-255-1-119.ip4.superloop.au) |
| 2025-03-22 22:00:31 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |