Newest at the top
| 2025-10-27 04:54:14 +0100 | synchromesh | (~john@2406:5a00:2412:2c00:5ca1:546e:8b5a:71bf) (Read error: Connection reset by peer) |
| 2025-10-27 04:54:14 +0100 | dtman34 | (~dtman34@2601:447:d182:6512:c2f9:c3a:b83d:6490) dtman34 |
| 2025-10-27 04:53:19 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds) |
| 2025-10-27 04:46:42 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-10-27 04:46:03 +0100 | td_ | (~td@i5387093E.versanet.de) td_ |
| 2025-10-27 04:44:08 +0100 | td_ | (~td@i53870936.versanet.de) (Ping timeout: 240 seconds) |
| 2025-10-27 04:39:58 +0100 | chromoblob | (~chromoblo@user/chromob1ot1c) chromoblob\0 |
| 2025-10-27 04:39:43 +0100 | chromoblob | (~chromoblo@user/chromob1ot1c) (Ping timeout: 246 seconds) |
| 2025-10-27 04:35:44 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds) |
| 2025-10-27 04:34:03 +0100 | dtman34 | (~dtman34@2601:447:d182:6512:c2f9:c3a:b83d:6490) (Ping timeout: 252 seconds) |
| 2025-10-27 04:30:52 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-10-27 04:20:25 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2025-10-27 04:15:28 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-10-27 04:13:22 +0100 | peterbecich | (~Thunderbi@172.222.148.214) (Ping timeout: 240 seconds) |
| 2025-10-27 04:10:11 +0100 | dtman34 | (~dtman34@2601:447:d182:6512:c2f9:c3a:b83d:6490) dtman34 |
| 2025-10-27 04:08:31 +0100 | annamalai | (~annamalai@157.49.214.182) annamalai |
| 2025-10-27 04:04:31 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds) |
| 2025-10-27 03:59:40 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-10-27 03:55:37 +0100 | lol__ | jcarpenter2 |
| 2025-10-27 03:49:44 +0100 | <haskellbridge> | <sm> this is engineering, people are operating in many different contexts, there are tradeoffs. I appreciate people exploring different approaches (leading to better understanding and consensus over time) |
| 2025-10-27 03:49:00 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds) |
| 2025-10-27 03:47:21 +0100 | <haskellbridge> | <sm> if you are still trying to blame (some part of) stack", I won't stop you. I'll also continue to push back when I see advice that misleads new haskellers |
| 2025-10-27 03:44:25 +0100 | werneta | (~werneta@71.83.160.242) (Quit: Lost terminal) |
| 2025-10-27 03:43:53 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-10-27 03:40:35 +0100 | <jackdk> | correction, the policy encouraged by *old templates instantiated by* the stack binary |
| 2025-10-27 03:40:07 +0100 | <jackdk> | Because I am very pro-upper-bounds + relaxation, I consider the real problem to be that 25 releases were left lying around waiting to be broken by a dependency that introduced a breaking change, and that the policy encouraged by the behaviour of the stack binary pushes the cost of reacting to that breaking change onto everyone else except the maintainer. |
| 2025-10-27 03:38:02 +0100 | <haskellbridge> | <sm> the dynamic solver doesn't think like a human and isn't good at explaining what it's doing |
| 2025-10-27 03:37:34 +0100 | <haskellbridge> | <sm> though usually only some other problem constraint causes it to go so far back |
| 2025-10-27 03:36:47 +0100 | <haskellbridge> | <sm> yes, that's the nature of cabal |
| 2025-10-27 03:35:02 +0100 | dtman34 | (~dtman34@2601:447:d182:6512:c2f9:c3a:b83d:6490) (Ping timeout: 240 seconds) |
| 2025-10-27 03:33:07 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds) |
| 2025-10-27 03:29:09 +0100 | machinedgod | (~machinedg@d75-159-126-101.abhsia.telus.net) (Ping timeout: 256 seconds) |
| 2025-10-27 03:28:20 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-10-27 03:24:15 +0100 | dtman34 | (~dtman34@2601:447:d182:6512:c2f9:c3a:b83d:6490) dtman34 |
| 2025-10-27 03:19:49 +0100 | <jackdk> | sm: re: "bravo for revising past releases. (I usually don't go that far back)." The thing is, I *had* to, because the lack of upper bounds on `aeson` meant that `cabal` kept selecting older and older releases in the build plan until I revised them all. |
| 2025-10-27 03:19:35 +0100 | dtman34 | (~dtman34@c-73-242-68-179.hsd1.mn.comcast.net) (Ping timeout: 244 seconds) |
| 2025-10-27 03:19:29 +0100 | pr1sm | (~pr1sm@24.91.163.31) (Remote host closed the connection) |
| 2025-10-27 03:17:51 +0100 | Maxdamantus | (~Maxdamant@user/maxdamantus) Maxdamantus |
| 2025-10-27 03:17:18 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) bitdex |
| 2025-10-27 03:16:55 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds) |
| 2025-10-27 03:15:43 +0100 | Maxdamantus | (~Maxdamant@user/maxdamantus) (Ping timeout: 246 seconds) |
| 2025-10-27 03:15:37 +0100 | Tuplanolla | (~Tuplanoll@91-159-187-167.elisa-laajakaista.fi) (Ping timeout: 264 seconds) |
| 2025-10-27 03:11:44 +0100 | Shark8 | (~Shark8@c-174-56-102-109.hsd1.nm.comcast.net) (Ping timeout: 240 seconds) |
| 2025-10-27 03:10:55 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) (Remote host closed the connection) |
| 2025-10-27 03:10:18 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-10-27 03:10:10 +0100 | ljdarj | (~Thunderbi@user/ljdarj) (Ping timeout: 256 seconds) |
| 2025-10-27 03:09:19 +0100 | Dhark8 | (~Shark8@c-174-56-102-109.hsd1.nm.comcast.net) (Ping timeout: 240 seconds) |
| 2025-10-27 03:09:05 +0100 | OWS | (~Shark8@c-174-56-102-109.hsd1.nm.comcast.net) |
| 2025-10-27 03:08:07 +0100 | haltingsolver | (~cmo@2604:3d09:207f:8000::d1dc) |
| 2025-10-27 03:07:45 +0100 | haltingsolver | (~cmo@2604:3d09:207f:8000::d1dc) (Remote host closed the connection) |