2025/10/27

Newest at the top

2025-10-27 22:15:10 +0100cstml(~cstml@user/cstml) (Quit: ZNC 1.10.1 - https://znc.in)
2025-10-27 22:12:50 +0100Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net)
2025-10-27 22:12:31 +0100Zemy(~Zemy@2600:100c:b046:9707:c36:41ff:feef:7f2c) (Ping timeout: 255 seconds)
2025-10-27 22:10:51 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-27 22:09:29 +0100trickard_(~trickard@cpe-55-98-47-163.wireline.com.au)
2025-10-27 22:09:15 +0100trickard_(~trickard@cpe-55-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2025-10-27 22:08:25 +0100Zemy_(~Zemy@12.50.228.210)
2025-10-27 22:04:45 +0100michalz(~michalz@185.246.207.221) (Remote host closed the connection)
2025-10-27 22:04:25 +0100 <haskellbridge> <Morj> I vaguely recall some options to at least distinguish evaluating an expression from realizing a derivation when running a command, to see which takes longer
2025-10-27 22:04:16 +0100haltingsolver(~cmo@2604:3d09:207f:8000::d1dc)
2025-10-27 22:03:50 +0100 <yushyin> usually there are mechanisms to cache the shell env, like nix-community/nix-direnv. don't know how to achieve this with stack+nix, though
2025-10-27 22:03:03 +0100 <haskellbridge> <magic_rb> There has been some developments in profiling and perf improvements but i havent tested them
2025-10-27 22:02:40 +0100 <haskellbridge> <magic_rb> There isnt great tooling anyway for that
2025-10-27 22:01:16 +0100qqe(~qqq@185.54.23.200) (Remote host closed the connection)
2025-10-27 22:00:55 +0100Zemy_(~Zemy@mobile-107-80-206-62.mycingular.net) (Ping timeout: 264 seconds)
2025-10-27 22:00:50 +0100Lycurgus(~juan@user/Lycurgus) Lycurgus
2025-10-27 22:00:18 +0100 <haskellbridge> <Morj> I'm not well versed enough to know how to profile nix
2025-10-27 22:00:01 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds)
2025-10-27 21:59:56 +0100 <haskellbridge> <Morj> «time nix-shell -p stack haskell.compiler.ghc98 --run exit» gives «real 0m7.712s»
2025-10-27 21:59:37 +0100 <haskellbridge> <Morj> Well, that's just nix? Some operations take long there
2025-10-27 21:58:55 +0100Zemy(~Zemy@2600:100c:b046:9707:c36:41ff:feef:7f2c)
2025-10-27 21:57:15 +0100tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net) (Quit: ksdsk)
2025-10-27 21:55:04 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-27 21:52:00 +0100 <haskellbridge> <sm> why does that take 10s ?
2025-10-27 21:51:54 +0100 <haskellbridge> <sm> ack
2025-10-27 21:46:48 +0100Zemy(~Zemy@2600:100c:b046:9707:7c26:54ff:fe94:28b9) (Ping timeout: 256 seconds)
2025-10-27 21:44:43 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds)
2025-10-27 21:44:32 +0100Zemy_(~Zemy@mobile-107-80-206-62.mycingular.net)
2025-10-27 21:41:25 +0100notzmv(~umar@user/notzmv) notzmv
2025-10-27 21:40:32 +0100 <haskellbridge> <Morj> What's not convenient is that now 'stack run' has to enter the shell every time which takes like 10 seconds
2025-10-27 21:40:07 +0100 <haskellbridge> <Morj> I just tried stack's nix integration. It's convenient
2025-10-27 21:39:17 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-27 21:35:46 +0100jmcantrell(~weechat@user/jmcantrell) jmcantrell
2025-10-27 21:31:03 +0100Zemy_(~Zemy@2600:100c:b046:9707:64c6:42ff:fe67:7876) (Read error: Connection reset by peer)
2025-10-27 21:31:03 +0100Zemy(~Zemy@2600:100c:b046:9707:7c26:54ff:fe94:28b9)
2025-10-27 21:28:13 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds)
2025-10-27 21:25:52 +0100Googulator79(~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu) (Quit: Client closed)
2025-10-27 21:25:38 +0100Googulator28(~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu)
2025-10-27 21:24:48 +0100humasect(~humasect@dyn-192-249-132-90.nexicom.net) (Remote host closed the connection)
2025-10-27 21:21:14 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-27 21:19:18 +0100Fijxu_(~Fijxu@user/fijxu) fijxu
2025-10-27 21:17:58 +0100sajith_(~sajith@user/sajith) sajith
2025-10-27 21:17:36 +0100sajith(~sajith@user/sajith) (Remote host closed the connection)
2025-10-27 21:17:27 +0100Zemy(~Zemy@72.178.108.235) (Ping timeout: 244 seconds)
2025-10-27 21:16:59 +0100Fijxu(~Fijxu@user/fijxu) (Quit: XD!!)
2025-10-27 21:16:50 +0100lortabac(~lortabac@mx1.fracta.dev) lortabac
2025-10-27 21:16:36 +0100lortabac(~lortabac@mx1.fracta.dev) (Read error: Connection reset by peer)
2025-10-27 21:15:24 +0100humasect(~humasect@dyn-192-249-132-90.nexicom.net) humasect
2025-10-27 21:14:34 +0100Zemy_(~Zemy@2600:100c:b046:9707:64c6:42ff:fe67:7876)
2025-10-27 21:12:27 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds)