2025/07/28

Newest at the top

2025-07-29 00:41:02 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-07-29 00:38:43 +0200caubert(~caubert@user/caubert) caubert
2025-07-29 00:38:37 +0200araujo(~araujo@216.73.163.169) araujo
2025-07-29 00:36:39 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-07-29 00:29:10 +0200dtman34(~dtman34@2601:447:d182:6512:c2f9:c3a:b83d:6490) (Ping timeout: 272 seconds)
2025-07-29 00:25:48 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds)
2025-07-29 00:25:34 +0200caubert(~caubert@user/caubert) (Ping timeout: 260 seconds)
2025-07-29 00:25:20 +0200biberu(~biberu@user/biberu) (Read error: Connection reset by peer)
2025-07-29 00:24:35 +0200 <dolio> I guess the answer to your implied question is that it's easier than graph isomorphism, because it's graph equality. It's only successful if the node names (package names + build flags) are exactly the same.
2025-07-29 00:21:15 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-07-29 00:19:56 +0200Sgeo(~Sgeo@user/sgeo) Sgeo
2025-07-29 00:15:30 +0200trickard_trickard
2025-07-29 00:15:00 +0200ljdarj(~Thunderbi@user/ljdarj) ljdarj
2025-07-29 00:11:16 +0200 <dolio> In the cabal case the mechanism is more like hash consing, I guess. Every time you build something you remember what options it and all its dependencies were built with, and store the result indexed by all that information. Then if that ever shows up again in a build plan, you use what you already built.
2025-07-29 00:10:42 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-07-29 00:05:52 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-07-29 00:00:56 +0200trickard_(~trickard@cpe-51-98-47-163.wireline.com.au)
2025-07-29 00:00:52 +0200 <dolio> Of <exp> that is.
2025-07-29 00:00:43 +0200 <dolio> If you write something like `case <exp> of <pattern> -> ... case <exp> of ...`, then I think it will do that CSE.
2025-07-29 00:00:42 +0200trickard_(~trickard@cpe-51-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2025-07-28 23:58:35 +0200 <dolio> GHC does some limited cases of it, though.
2025-07-28 23:58:18 +0200 <dolio> Also, it's not always an optimization.
2025-07-28 23:57:53 +0200 <dolio> It's an optimization you might try on code. Usually you wouldn't say you're going to guarantee there are no common subexpressions, just factor them out if you notice them.
2025-07-28 23:56:15 +0200 <jreicher> dolio: I didn't know anyone was trying to do something like CSE (haven't heard the term before). Sounds dangerously close to testing for graph isomorphism.
2025-07-28 23:55:09 +0200LainIwakura(~LainIwaku@user/LainIwakura) (Ping timeout: 272 seconds)
2025-07-28 23:54:50 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-07-28 23:51:26 +0200DoNald(~aa@110.137.36.197) (Remote host closed the connection)
2025-07-28 23:50:28 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-07-28 23:49:17 +0200humasect(~humasect@dyn-192-249-132-90.nexicom.net) (Quit: Leaving...)
2025-07-28 23:48:16 +0200LainIwakura(~LainIwaku@user/LainIwakura) LainIwakura
2025-07-28 23:45:10 +0200libertyprime(~libertypr@118.92.81.152) libertyprime
2025-07-28 23:44:54 +0200libertyprime(~libertypr@118.92.81.152) (Ping timeout: 260 seconds)
2025-07-28 23:40:56 +0200bw(sid2730@user/betawaffle) betawaffle
2025-07-28 23:40:53 +0200ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 252 seconds)
2025-07-28 23:40:38 +0200bw(sid2730@user/betawaffle) (Server closed connection)
2025-07-28 23:40:00 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 276 seconds)
2025-07-28 23:39:58 +0200sam113102sam113101
2025-07-28 23:39:55 +0200sam113101(~sam@modemcable200.189-202-24.mc.videotron.ca) (Remote host closed the connection)
2025-07-28 23:39:30 +0200sam113102(~sam@modemcable200.189-202-24.mc.videotron.ca) sam113101
2025-07-28 23:37:54 +0200Henson(~kvirc@192-0-202-2.cpe.teksavvy.com) (Ping timeout: 260 seconds)
2025-07-28 23:37:39 +0200libertyprime(~libertypr@118.92.81.152) libertyprime
2025-07-28 23:35:06 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-07-28 23:32:59 +0200LainIwakura(~LainIwaku@user/LainIwakura) (Ping timeout: 272 seconds)
2025-07-28 23:29:28 +0200target_i(~target_i@user/target-i/x-6023099) (Quit: leaving)
2025-07-28 23:24:14 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds)
2025-07-28 23:23:44 +0200arahael(~arahael@user/arahael) (Ping timeout: 260 seconds)
2025-07-28 23:17:03 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-07-28 23:10:36 +0200michalz_(~michalz@185.246.207.217) (Remote host closed the connection)
2025-07-28 23:10:22 +0200Square2(~Square@user/square) Square
2025-07-28 23:06:14 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds)