2025/04/08

Newest at the top

2025-04-08 10:04:15 +0200dhil(~dhil@2a0c:b381:52e:3600:103b:c63d:9624:f51b) dhil
2025-04-08 09:58:43 +0200sord937(~sord937@gateway/tor-sasl/sord937) sord937
2025-04-08 09:58:24 +0200sord937(~sord937@gateway/tor-sasl/sord937) (Remote host closed the connection)
2025-04-08 09:54:53 +0200machinedgod(~machinedg@d108-173-18-100.abhsia.telus.net) machinedgod
2025-04-08 09:53:50 +0200polyphem(~rod@p4fc2cb32.dip0.t-ipconnect.de) polyphem
2025-04-08 09:53:20 +0200merijn(~merijn@77.242.116.146) merijn
2025-04-08 09:43:08 +0200emmanuelux(~emmanuelu@user/emmanuelux) (Read error: Connection reset by peer)
2025-04-08 09:40:24 +0200lxsameer(~lxsameer@Serene/lxsameer) lxsameer
2025-04-08 09:36:25 +0200acidjnk_new3(~acidjnk@p200300d6e71c4f636055d0f69fb4dc8c.dip0.t-ipconnect.de) acidjnk
2025-04-08 09:35:59 +0200 <Axman6> absolutely
2025-04-08 09:35:31 +0200 <jackdk> Axman6: if you had your way, everything would either be `coerce` or `id`
2025-04-08 09:33:33 +0200fp1(~Thunderbi@wireless-86-50-140-125.open.aalto.fi) (Ping timeout: 268 seconds)
2025-04-08 09:24:56 +0200sord937(~sord937@gateway/tor-sasl/sord937) sord937
2025-04-08 09:23:57 +0200sord937(~sord937@gateway/tor-sasl/sord937) (Remote host closed the connection)
2025-04-08 09:18:52 +0200Lord_of_Life_Lord_of_Life
2025-04-08 09:17:29 +0200Lord_of_Life(~Lord@user/lord-of-life/x-2819915) (Ping timeout: 252 seconds)
2025-04-08 09:17:29 +0200Lord_of_Life_(~Lord@user/lord-of-life/x-2819915) Lord_of_Life
2025-04-08 09:16:07 +0200tavare(~tavare@user/tavare) (Remote host closed the connection)
2025-04-08 09:10:51 +0200foul_owl(~kerry@94.156.149.99) foul_owl
2025-04-08 09:03:56 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-04-08 09:03:11 +0200lortabac(~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4)
2025-04-08 09:01:03 +0200caconym(~caconym@user/caconym) caconym
2025-04-08 09:00:01 +0200caconym(~caconym@user/caconym) (Quit: bye)
2025-04-08 08:58:58 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-04-08 08:54:06 +0200foul_owl(~kerry@94.156.149.96) (Read error: Connection reset by peer)
2025-04-08 08:51:52 +0200tromp(~textual@2001:1c00:3487:1b00:1419:ab0:498a:2d0c)
2025-04-08 08:49:58 +0200Sgeo(~Sgeo@user/sgeo) (Read error: Connection reset by peer)
2025-04-08 08:48:10 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds)
2025-04-08 08:45:34 +0200tromp(~textual@2001:1c00:3487:1b00:1419:ab0:498a:2d0c) (Client Quit)
2025-04-08 08:44:51 +0200tromp(~textual@2001:1c00:3487:1b00:1419:ab0:498a:2d0c)
2025-04-08 08:44:43 +0200 <Axman6> See https://accidentallyquadratic.tumblr.com/tagged/haskell for some examples
2025-04-08 08:43:40 +0200 <Axman6> where might be benefits to doing that too, as the explicit lambda might actually get allocated - reminds me of an accidentally quadratic bug in cabal years ago
2025-04-08 08:43:11 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-04-08 08:42:45 +0200 <Axman6> I have a feeling that rewrapCo f = Coroutine $ ReaderT (\c -> ExceptT (Identity (f c))) can become rewrapCo f = coerce f
2025-04-08 08:41:58 +0200 <Axman6> (your coroutine code)_
2025-04-08 08:41:47 +0200 <Axman6> part of me really wants to replace so much of that code with coerce
2025-04-08 08:41:33 +0200ft(~ft@p508db463.dip0.t-ipconnect.de) (Quit: leaving)
2025-04-08 08:41:12 +0200 <Axman6> um, it might be https://downloads.haskell.org/ghc/latest/docs/users_guide/profiling.html#rts-flag-hm or -hi used with https://downloads.haskell.org/ghc/latest/docs/users_guide/debug-info.html#ghc-flag-finfo-table-map
2025-04-08 08:38:57 +0200halloy2596(~halloy259@2607:ac80:411:a:dc3c:8e7b:ab32:5495) (Client Quit)
2025-04-08 08:38:28 +0200halloy2596(~halloy259@2607:ac80:411:a:dc3c:8e7b:ab32:5495)
2025-04-08 08:34:18 +0200CiaoSen(~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) CiaoSen
2025-04-08 08:32:23 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-04-08 08:30:39 +0200sord937(~sord937@gateway/tor-sasl/sord937) sord937
2025-04-08 08:27:23 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-04-08 08:25:02 +0200fp1(~Thunderbi@wireless-86-50-140-125.open.aalto.fi) fp
2025-04-08 08:23:39 +0200 <emojelly> Ah, do you happen to know which one?
2025-04-08 08:22:28 +0200 <Axman6> There's some new flag that tags each allocation with its location IIRC. not sure exactly how helpful that'd be for short lived stuff
2025-04-08 08:21:51 +0200 <emojelly> I wish I could figure out what and why...
2025-04-08 08:20:47 +0200 <Axman6> seems likely
2025-04-08 08:20:23 +0200 <emojelly> What does that mean? That there is a lot of really shortlived data?