2026/02/24

Newest at the top

2026-02-24 05:26:39 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-02-24 05:23:56 +0100lisbeths(uid135845@id-135845.lymington.irccloud.com) lisbeths
2026-02-24 05:21:17 +0100lbseale(~quassel@user/ep1ctetus) ep1ctetus
2026-02-24 05:20:33 +0100lbseale(~quassel@user/ep1ctetus) (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)
2026-02-24 05:20:19 +0100eL_Bart0(eL_Bart02@dietunichtguten.org)
2026-02-24 05:20:06 +0100eL_Bart0-(eL_Bart02@dietunichtguten.org) (Server closed connection)
2026-02-24 05:18:18 +0100 <monochrom> Oh oops yeah that's an upper bound.
2026-02-24 05:18:07 +0100ec(~ec@gateway/tor-sasl/ec) ec
2026-02-24 05:17:42 +0100ec(~ec@gateway/tor-sasl/ec) (Remote host closed the connection)
2026-02-24 05:16:03 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 255 seconds)
2026-02-24 05:11:17 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-02-24 05:09:55 +0100arahael(~wetfoot@user/arahael) (Ping timeout: 265 seconds)
2026-02-24 05:09:40 +0100 <Leary> But the alternative of refusing to build what would have succeeded doesn't really seem better; either way the bound is wrong and you're relying on intrepid explorers to eventually correct it.
2026-02-24 05:09:15 +0100 <Leary> Reflecting things a bit, your point seems to be that an older version of a dependency (than is implicitly assumed) may be used to build the package, causing it to fail.
2026-02-24 05:08:53 +0100 <Leary> In that particular case, I think the actual issue is importing without concern for namespace pollution. Also, that's an upper bound?
2026-02-24 05:00:20 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2026-02-24 05:00:19 +0100ChanServ+v yahb2
2026-02-24 05:00:19 +0100yahb2(~yahb2@user/tomsmeding/bot/yahb2) yahb2
2026-02-24 04:59:57 +0100yahb2(~yahb2@user/tomsmeding/bot/yahb2) (Server closed connection)
2026-02-24 04:55:56 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-02-24 04:47:38 +0100APic(apic@apic.name) APic
2026-02-24 04:47:26 +0100 <monochrom> So if you set a lower bound like <=1.14 or 1.13, the worst that can happen is cabal downloads and builds an appropriate version of time. If you don't set a lower bound, now you have to set a lower bound.
2026-02-24 04:47:26 +0100APic(apic@apic.name) (Server closed connection)
2026-02-24 04:45:53 +0100 <monochrom> (time-1.15 adds new pattern synonyms that name-clashes with someone's existing code that assumes <=1.14)
2026-02-24 04:45:11 +0100 <monochrom> Then one day you will run into something like this recent example: https://discourse.haskell.org/t/breaking-changes-in-time-1-15-ghc-9-14/13711
2026-02-24 04:45:00 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 255 seconds)
2026-02-24 04:44:59 +0100xff0x_xff0x
2026-02-24 04:44:13 +0100peterbecich(~Thunderbi@71.84.33.135) peterbecich
2026-02-24 04:42:45 +0100xff0x(~xff0x@fsb6a9491c.tkyc517.ap.nuro.jp) (Ping timeout: 255 seconds)
2026-02-24 04:41:24 +0100machinedgod(~machinedg@d172-219-48-230.abhsia.telus.net) (Ping timeout: 255 seconds)
2026-02-24 04:41:00 +0100arandombit(~arandombi@user/arandombit) (Ping timeout: 256 seconds)
2026-02-24 04:40:40 +0100xff0x_(~xff0x@fsb6a9491c.tkyc517.ap.nuro.jp)
2026-02-24 04:40:34 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-02-24 04:40:33 +0100werneta(~werneta@71.83.160.242) werneta
2026-02-24 04:39:28 +0100 <Leary> Well, in that case you're setting them conservatively. I was more wondering about the opposite strategy of omitting them entirely.
2026-02-24 04:34:26 +0100 <monochrom> I usually do. I set my lower bounds to be what I happen to have when I start the project. Then I don't change them until someone wants it changed.
2026-02-24 04:29:40 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds)
2026-02-24 04:28:36 +0100Lord_of_Life(~Lord@user/lord-of-life/x-2819915) Lord_of_Life
2026-02-24 04:28:08 +0100haskell-noob(~haskell-n@50.35.80.129) (Quit: Client closed)
2026-02-24 04:27:49 +0100humasect(~humasect@dyn-192-249-132-90.nexicom.net) humasect
2026-02-24 04:27:37 +0100Lord_of_Life(~Lord@user/lord-of-life/x-2819915) (Quit: Laa shay'a waqi'un moutlaq bale kouloun moumkine)
2026-02-24 04:25:12 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-02-24 04:25:06 +0100 <Leary> Upper bounds aside, `cabal check` doesn't seem to care about lower bounds. Does that mean I can give up on the archaeology necessary to find them?
2026-02-24 04:21:46 +0100arandombit(~arandombi@user/arandombit) arandombit
2026-02-24 04:21:36 +0100Logio(em@kapsi.fi) Logio
2026-02-24 04:21:26 +0100Logio(em@kapsi.fi) (Server closed connection)
2026-02-24 04:16:46 +0100Googulator17(~Googulato@2a01-036d-0106-499d-1c5a-0e4b-5795-d7e3.pool6.digikabel.hu)
2026-02-24 04:16:31 +0100Googulator17(~Googulato@2a01-036d-0106-499d-1c5a-0e4b-5795-d7e3.pool6.digikabel.hu) (Quit: Client closed)
2026-02-24 04:14:03 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 268 seconds)
2026-02-24 04:07:10 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn