Newest at the top
| 2026-02-24 05:52:48 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-24 05:49:04 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds) |
| 2026-02-24 05:47:32 +0100 | doyougnu | (~doyougnu@38.175.72.111) doyougnu |
| 2026-02-24 05:46:46 +0100 | doyougnu | (~doyougnu@38.175.72.111) (Server closed connection) |
| 2026-02-24 05:43:37 +0100 | michalz | (~michalz@185.246.207.221) |
| 2026-02-24 05:43:03 +0100 | Athas | (athas@2a01:7c8:aaac:1cf:10a0:cce8:21cf:53aa) |
| 2026-02-24 05:42:51 +0100 | Athas | (athas@2a01:7c8:aaac:1cf:acb7:4f2b:6164:21c9) (Quit: ZNC 1.9.1 - https://znc.in) |
| 2026-02-24 05:42:01 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-24 05:32:54 +0100 | eso | (a0662dfd5e@2a03:6000:1812:100::1266) jeso |
| 2026-02-24 05:32:49 +0100 | <geekosaur> | and leaving either off forces others to do it for you by their tripping over it |
| 2026-02-24 05:32:46 +0100 | eso | (a0662dfd5e@2a03:6000:1812:100::1266) (Server closed connection) |
| 2026-02-24 05:32:27 +0100 | <geekosaur> | ithis is a long-running argument, and there are no real solutions because you can't reliably infer upper or lower bounds; you or someone else must experiment or actively test |
| 2026-02-24 05:31:21 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 255 seconds) |
| 2026-02-24 05:26:39 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-24 05:23:56 +0100 | lisbeths | (uid135845@id-135845.lymington.irccloud.com) lisbeths |
| 2026-02-24 05:21:17 +0100 | lbseale | (~quassel@user/ep1ctetus) ep1ctetus |
| 2026-02-24 05:20:33 +0100 | lbseale | (~quassel@user/ep1ctetus) (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) |
| 2026-02-24 05:20:19 +0100 | eL_Bart0 | (eL_Bart02@dietunichtguten.org) |
| 2026-02-24 05:20:06 +0100 | eL_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 +0100 | ec | (~ec@gateway/tor-sasl/ec) ec |
| 2026-02-24 05:17:42 +0100 | ec | (~ec@gateway/tor-sasl/ec) (Remote host closed the connection) |
| 2026-02-24 05:16:03 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 255 seconds) |
| 2026-02-24 05:11:17 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-24 05:09:55 +0100 | arahael | (~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 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2026-02-24 05:00:19 +0100 | ChanServ | +v yahb2 |
| 2026-02-24 05:00:19 +0100 | yahb2 | (~yahb2@user/tomsmeding/bot/yahb2) yahb2 |
| 2026-02-24 04:59:57 +0100 | yahb2 | (~yahb2@user/tomsmeding/bot/yahb2) (Server closed connection) |
| 2026-02-24 04:55:56 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-24 04:47:38 +0100 | APic | (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 +0100 | APic | (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 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 255 seconds) |
| 2026-02-24 04:44:59 +0100 | xff0x_ | xff0x |
| 2026-02-24 04:44:13 +0100 | peterbecich | (~Thunderbi@71.84.33.135) peterbecich |
| 2026-02-24 04:42:45 +0100 | xff0x | (~xff0x@fsb6a9491c.tkyc517.ap.nuro.jp) (Ping timeout: 255 seconds) |
| 2026-02-24 04:41:24 +0100 | machinedgod | (~machinedg@d172-219-48-230.abhsia.telus.net) (Ping timeout: 255 seconds) |
| 2026-02-24 04:41:00 +0100 | arandombit | (~arandombi@user/arandombit) (Ping timeout: 256 seconds) |
| 2026-02-24 04:40:40 +0100 | xff0x_ | (~xff0x@fsb6a9491c.tkyc517.ap.nuro.jp) |
| 2026-02-24 04:40:34 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-24 04:40:33 +0100 | werneta | (~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 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds) |