Newest at the top
| 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) |
| 2026-02-24 04:28:36 +0100 | Lord_of_Life | (~Lord@user/lord-of-life/x-2819915) Lord_of_Life |
| 2026-02-24 04:28:08 +0100 | haskell-noob | (~haskell-n@50.35.80.129) (Quit: Client closed) |
| 2026-02-24 04:27:49 +0100 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) humasect |
| 2026-02-24 04:27:37 +0100 | Lord_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 +0100 | merijn | (~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 +0100 | arandombit | (~arandombi@user/arandombit) arandombit |
| 2026-02-24 04:21:36 +0100 | Logio | (em@kapsi.fi) Logio |
| 2026-02-24 04:21:26 +0100 | Logio | (em@kapsi.fi) (Server closed connection) |
| 2026-02-24 04:16:46 +0100 | Googulator17 | (~Googulato@2a01-036d-0106-499d-1c5a-0e4b-5795-d7e3.pool6.digikabel.hu) |
| 2026-02-24 04:16:31 +0100 | Googulator17 | (~Googulato@2a01-036d-0106-499d-1c5a-0e4b-5795-d7e3.pool6.digikabel.hu) (Quit: Client closed) |
| 2026-02-24 04:14:03 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 268 seconds) |
| 2026-02-24 04:07:10 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-24 03:56:43 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2026-02-24 03:55:40 +0100 | peterbecich | (~Thunderbi@71.84.33.135) (Ping timeout: 256 seconds) |
| 2026-02-24 03:51:53 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-24 03:49:08 +0100 | Googulator17 | (~Googulato@2a01-036d-0106-499d-1c5a-0e4b-5795-d7e3.pool6.digikabel.hu) |
| 2026-02-24 03:48:53 +0100 | Googulator17 | (~Googulato@2a01-036d-0106-499d-1c5a-0e4b-5795-d7e3.pool6.digikabel.hu) (Quit: Client closed) |
| 2026-02-24 03:48:46 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 268 seconds) |
| 2026-02-24 03:47:53 +0100 | hook54321 | (sid149355@user/hook54321) hook54321 |
| 2026-02-24 03:46:37 +0100 | hook54321 | (sid149355@user/hook54321) (Server closed connection) |
| 2026-02-24 03:44:06 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-24 03:36:01 +0100 | bjorkintosh | (~bjork@user/bjorkintosh) (Leaving) |
| 2026-02-24 03:36:00 +0100 | bjorkintosh | (~bjork@user/bjorkintosh) bjorkintosh |
| 2026-02-24 03:34:18 +0100 | piele | (~piele@eiseth.creativeserver.net) |
| 2026-02-24 03:34:06 +0100 | piele | (~piele@eiseth.creativeserver.net) (Server closed connection) |
| 2026-02-24 03:33:43 +0100 | jtnuttall | (~jeremy@user/jeremyn) jeremyn |
| 2026-02-24 03:33:13 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds) |