2025/10/28

Newest at the top

2025-10-28 22:19:00 +0100Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net)
2025-10-28 22:16:43 +0100Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 244 seconds)
2025-10-28 22:15:50 +0100Googulator94(~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu)
2025-10-28 22:15:47 +0100Googulator46(~Googulato@84-236-65-182.pool.digikabel.hu) (Quit: Client closed)
2025-10-28 22:13:50 +0100Wbooze(~wboozE@2a02:8071:57a1:dc0:a984:f47b:49ad:2bc0) (Read error: Connection reset by peer)
2025-10-28 22:13:31 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds)
2025-10-28 22:13:21 +0100__monty__(~toonn@user/toonn) (Quit: leaving)
2025-10-28 22:12:35 +0100foo3(~Square@user/square) (Ping timeout: 244 seconds)
2025-10-28 22:04:44 +0100target_i(~target_i@user/target-i/x-6023099) (Quit: leaving)
2025-10-28 22:04:39 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-28 22:04:14 +0100 <talismanick> Has anyone tried ghc->wasm->android?
2025-10-28 22:03:04 +0100talismanick(~user@2601:644:937c:ed10::b832) talismanick
2025-10-28 22:01:19 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds)
2025-10-28 21:58:32 +0100gustrb(~gustrb@user/gustrb) gustrb
2025-10-28 21:58:32 +0100gustrb(~gustrb@191.243.134.87) (Changing host)
2025-10-28 21:58:08 +0100gustrb(~gustrb@191.243.134.87)
2025-10-28 21:57:52 +0100gustrb(~gustrb@191.243.134.87) (Client Quit)
2025-10-28 21:57:46 +0100gustrb(~gustrb@191.243.134.87)
2025-10-28 21:57:27 +0100gustrb(~gustrb@user/gustrb) (Quit: gustrb)
2025-10-28 21:54:07 +0100LainIwakura(~LainIwaku@user/LainIwakura) (Ping timeout: 250 seconds)
2025-10-28 21:48:42 +0100LainIwakura85(~LainIwaku@user/LainIwakura) LainIwakura
2025-10-28 21:46:20 +0100LainIwakura(~LainIwaku@user/LainIwakura) LainIwakura
2025-10-28 21:45:42 +0100Googulator46(~Googulato@84-236-65-182.pool.digikabel.hu)
2025-10-28 21:45:41 +0100Googulator(~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu) (Quit: Client closed)
2025-10-28 21:45:00 +0100vgtw_(~vgtw@user/vgtw) (Ping timeout: 256 seconds)
2025-10-28 21:44:12 +0100vgtw(~vgtw@user/vgtw) vgtw
2025-10-28 21:41:11 +0100travv0(uid293381@user/travv0) (Quit: Connection closed for inactivity)
2025-10-28 21:33:01 +0100Xe(~Xe@perl/impostor/xe) (Ping timeout: 264 seconds)
2025-10-28 21:31:49 +0100Xe_(~Xe@perl/impostor/xe) Xe
2025-10-28 21:28:36 +0100 <merijn> Unfortunate, but I think you'd have to hack something together yourself
2025-10-28 21:27:16 +0100Googulator(~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu)
2025-10-28 21:26:58 +0100Googulator(~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu) (Quit: Client closed)
2025-10-28 21:25:43 +0100 <Ptival> Here the main dev wants to keep writing package.yaml
2025-10-28 21:24:30 +0100 <merijn> I mean, stack also works with just a cabal file and no hpack, eliminating one level of potential mismatches
2025-10-28 21:23:39 +0100 <Ptival> That's my use case. Main dev is a stack user, I prefer cabal, and things gets out of sync. In CI, it's easy to check that the current .cabal matches package.yaml by calling hpack, and essentially I'd want the same checks for the files I mentioned. It's a pretty easy script, just don't want to reinvent the wheel if it exists.
2025-10-28 21:17:05 +0100ski(~ski@remote11.chalmers.se) ski
2025-10-28 21:15:53 +0100Googulator12Googulator
2025-10-28 21:15:47 +0100Googulator(~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu) (Quit: Client closed)
2025-10-28 21:15:40 +0100Googulator12(~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu)
2025-10-28 21:14:06 +0100 <tomsmeding> well, a use case is having a project that you want to be conveniently buildable by as many people as possible. But I also don't know of such a tool
2025-10-28 21:12:36 +0100CiaoSen(~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) CiaoSen
2025-10-28 21:12:20 +0100jreicher(~user@user/jreicher) (Quit: In transit)
2025-10-28 21:07:23 +0100Googulator52Googulator
2025-10-28 21:02:21 +0100Googulator52(~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu)
2025-10-28 21:02:10 +0100Googulator52(~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu) (Quit: Client closed)
2025-10-28 20:56:28 +0100 <merijn> I doubt such a thing exists. I suspect the overlap of those two use-cases is practically the empty set
2025-10-28 20:50:35 +0100 <Ptival> Does someone know a tool / CI script / whatever that checks for discrepancies between a stack.yaml and a cabal.project? e.g. listing the same source repos at the same tags
2025-10-28 20:49:26 +0100Ptival(~Ptival@user/Ptival) Ptival
2025-10-28 20:49:26 +0100Ptival(~Ptival@2601:1c0:5f00:27e0:8cd:539e:652c:5dd5) (Changing host)
2025-10-28 20:48:45 +0100Ptival(~Ptival@2601:1c0:5f00:27e0:8cd:539e:652c:5dd5)