2024/04/27

Newest at the top

2024-04-27 08:33:40 +0200Inst(~Inst@user/Inst) (Ping timeout: 245 seconds)
2024-04-27 08:33:13 +0200danza(~francesco@151.37.225.196)
2024-04-27 08:32:49 +0200danza(~francesco@151.37.225.196) (Remote host closed the connection)
2024-04-27 08:28:25 +0200 <probie> `ghc-pkg latest template-haskell` probably
2024-04-27 08:25:34 +0200bliminse(~bliminse@user/bliminse) (Quit: leaving)
2024-04-27 08:24:08 +0200yeitrafferin(~user@2a04:4540:7202:7600:9288:54b5:ce2d:f3dc)
2024-04-27 08:21:55 +0200tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2024-04-27 08:20:05 +0200phma(phma@2001:5b0:210d:77f8:690d:ee85:cd6a:7031)
2024-04-27 08:18:58 +0200phma(phma@2001:5b0:210f:2ed8:1686:9f1d:3773:c78f) (Read error: Connection reset by peer)
2024-04-27 08:16:40 +0200 <bsima> I look at the .version field in nixpkgs and its null
2024-04-27 08:16:34 +0200 <bsima> how do I find out what version of template-haskell is shipped with my ghc version?
2024-04-27 08:10:06 +0200tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2024-04-27 08:04:22 +0200tri(~tri@ool-18bc2e74.dyn.optonline.net) (Remote host closed the connection)
2024-04-27 07:57:47 +0200Inst(~Inst@user/Inst)
2024-04-27 07:49:49 +0200robobub(uid248673@id-248673.uxbridge.irccloud.com)
2024-04-27 07:43:22 +0200harveypwca(~harveypwc@2601:246:d080:b40:1889:d9bf:2dd8:b288)
2024-04-27 07:27:20 +0200danza(~francesco@151.37.225.196)
2024-04-27 07:10:48 +0200rosco(~rosco@yp-146-6.tm.net.my)
2024-04-27 07:05:09 +0200pavonia(~user@user/siracusa) (Quit: Bye!)
2024-04-27 07:03:21 +0200machinedgod(~machinedg@d173-183-246-216.abhsia.telus.net) (Ping timeout: 256 seconds)
2024-04-27 07:00:11 +0200takuan(~takuan@178-116-218-225.access.telenet.be)
2024-04-27 06:59:31 +0200takuan(~takuan@178-116-218-225.access.telenet.be) (Read error: Connection reset by peer)
2024-04-27 06:58:34 +0200takuan(~takuan@178-116-218-225.access.telenet.be)
2024-04-27 06:25:28 +0200zmt00(~zmt00@user/zmt00)
2024-04-27 06:12:33 +0200swamp_(~zmt00@user/zmt00) (Read error: Connection reset by peer)
2024-04-27 06:01:21 +0200tdlgalt^(~cd@c-98-242-74-66.hsd1.ga.comcast.net) (Remote host closed the connection)
2024-04-27 06:01:06 +0200yin(~yin@user/zero) (Ping timeout: 252 seconds)
2024-04-27 05:57:39 +0200 <dmj`> probie: and yes
2024-04-27 05:57:32 +0200 <dmj`> probie: if we had haskellton, we wouldn't eat as much memory
2024-04-27 05:47:33 +0200Pixi(~Pixi@user/pixi)
2024-04-27 05:45:26 +0200 <monochrom> That too. :)
2024-04-27 05:45:26 +0200Pixi(~Pixi@user/pixi) (Quit: Leaving)
2024-04-27 05:45:18 +0200 <monochrom> Yeah.
2024-04-27 05:45:16 +0200 <probie> or just something that eats absurd amounts of RAM (which GHC seems quite capable of doing on its own)
2024-04-27 05:44:38 +0200 <probie> As in a full program optimising compiler?
2024-04-27 05:39:35 +0200tdlgalt^(~cd@c-98-242-74-66.hsd1.ga.comcast.net)
2024-04-27 05:36:12 +0200y04nn(~username@2a03:1b20:8:f011::e10d)
2024-04-27 05:34:10 +0200 <dmj`> monochrom: we need haskellton
2024-04-27 05:12:31 +0200aforemny_(~aforemny@2001:9e8:6cf4:e200:c321:623a:48be:28f1) (Ping timeout: 268 seconds)
2024-04-27 05:11:18 +0200madeleine-sydney(~madeleine@c-76-155-235-153.hsd1.co.comcast.net) (Quit: Konversation terminated!)
2024-04-27 05:10:59 +0200aforemny(~aforemny@i59F516DA.versanet.de)
2024-04-27 05:07:16 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex)
2024-04-27 05:06:11 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex) (Remote host closed the connection)
2024-04-27 05:02:28 +0200tri(~tri@ool-18bc2e74.dyn.optonline.net)
2024-04-27 04:59:47 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex)
2024-04-27 04:50:32 +0200madeleine-sydney(~madeleine@c-76-155-235-153.hsd1.co.comcast.net)
2024-04-27 04:50:25 +0200yin(~yin@user/zero)
2024-04-27 04:35:32 +0200Rodney_(~Rodney@176.254.244.83)
2024-04-27 04:34:49 +0200td_(~td@i5387091B.versanet.de)
2024-04-27 04:34:12 +0200Rodney_(~Rodney@176.254.244.83) (Ping timeout: 252 seconds)