2025/02/02

Newest at the top

2025-02-02 14:50:45 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-02-02 14:39:55 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds)
2025-02-02 14:35:23 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-02-02 14:33:45 +0100euleritian(~euleritia@dynamic-176-006-139-244.176.6.pool.telefonica.de)
2025-02-02 14:32:54 +0100euleritian(~euleritia@ip4d17fae8.dynamic.kabel-deutschland.de) (Ping timeout: 260 seconds)
2025-02-02 14:31:17 +0100lisbeths(~user@2603:3023:4be:4000:216:3eff:fe17:d69d) lisbeths
2025-02-02 14:25:09 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 276 seconds)
2025-02-02 14:20:29 +0100ljdarj(~Thunderbi@user/ljdarj) ljdarj
2025-02-02 14:20:01 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-02-02 14:16:59 +0100lisbeths(~user@2603:3023:4be:4000:216:3eff:fe17:d69d) (Ping timeout: 260 seconds)
2025-02-02 14:12:09 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 276 seconds)
2025-02-02 14:11:49 +0100RaedAddala(~RaedAddal@41.229.252.60)
2025-02-02 14:08:40 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-02-02 14:07:37 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-02-02 14:02:16 +0100euleritian(~euleritia@ip4d17fae8.dynamic.kabel-deutschland.de)
2025-02-02 14:01:58 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-02-02 14:01:36 +0100euleritian(~euleritia@dynamic-176-006-139-244.176.6.pool.telefonica.de) (Read error: Connection reset by peer)
2025-02-02 14:01:14 +0100tnt2tnt1
2025-02-02 14:01:14 +0100tnt1(~Thunderbi@user/tnt1) (Ping timeout: 260 seconds)
2025-02-02 14:00:11 +0100tnt2(~Thunderbi@user/tnt1) tnt1
2025-02-02 13:51:19 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds)
2025-02-02 13:49:21 +0100dysthesis(~dysthesis@user/dysthesis) dysthesis
2025-02-02 13:48:03 +0100eL_Bart0(eL_Bart0@dietunichtguten.org) (Ping timeout: 252 seconds)
2025-02-02 13:47:31 +0100tnt1(~Thunderbi@user/tnt1) tnt1
2025-02-02 13:47:17 +0100tnt1(~Thunderbi@user/tnt1) (Ping timeout: 248 seconds)
2025-02-02 13:46:51 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-02-02 13:44:02 +0100euleritian(~euleritia@dynamic-176-006-139-244.176.6.pool.telefonica.de)
2025-02-02 13:43:18 +0100euleritian(~euleritia@ip4d17fae8.dynamic.kabel-deutschland.de) (Ping timeout: 244 seconds)
2025-02-02 13:41:24 +0100ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 260 seconds)
2025-02-02 13:40:49 +0100tnt2tnt1
2025-02-02 13:40:48 +0100tnt1(~Thunderbi@user/tnt1) (Ping timeout: 245 seconds)
2025-02-02 13:39:50 +0100tnt2(~Thunderbi@user/tnt1) tnt1
2025-02-02 13:36:02 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-02-02 13:31:29 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-02-02 13:23:56 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 252 seconds)
2025-02-02 13:23:19 +0100smalltalkman(uid545680@id-545680.hampstead.irccloud.com) smalltalkman
2025-02-02 13:20:59 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds)
2025-02-02 13:19:33 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-02-02 13:17:48 +0100monochrom(trebla@216.138.220.146)
2025-02-02 13:16:07 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-02-02 13:14:42 +0100ljdarj(~Thunderbi@user/ljdarj) ljdarj
2025-02-02 13:11:28 +0100monochrom(trebla@216.138.220.146) (Ping timeout: 252 seconds)
2025-02-02 13:09:30 +0100 <lxsameer> wow this is amazing
2025-02-02 13:09:17 +0100 <lxsameer> perfect, thank you
2025-02-02 13:08:59 +0100 <geekosaur> https://gitlab.haskell.org/ghc/ghc/-/wikis/commentary
2025-02-02 13:08:30 +0100MyNetAz(~MyNetAz@user/MyNetAz) MyNetAz
2025-02-02 13:06:17 +0100 <lxsameer> geekosaur: interesting, is there any resource to get familiar with GHC internals? not in code level but an overview
2025-02-02 13:05:04 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds)
2025-02-02 13:03:36 +0100 <geekosaur> similarly, conceptually IO is best thought of as an impure program passed back to the RTS as the result of `main :: IO ()`, but ghc actually does something more performant
2025-02-02 13:02:57 +0100 <geekosaur> breaking things down to actual single parameter functions is certainly doable, but has lousy performance. so in terms of Haskell semantics it makes sense to think that way, but ghc goes for the more performant version