Newest at the top
| 2025-02-28 05:09:08 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-02-28 04:58:24 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds) |
| 2025-02-28 04:53:46 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-02-28 04:53:45 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 244 seconds) |
| 2025-02-28 04:49:28 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-02-28 04:46:25 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) bitdex |
| 2025-02-28 04:42:30 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2025-02-28 04:41:28 +0100 | k_hachig_ | (~k_hachig@bras-base-toroon0247w-grc-123-70-29-50-103.dsl.bell.ca) k_hachig |
| 2025-02-28 04:38:46 +0100 | fantom | (~fantom@2.219.56.221) (Ping timeout: 244 seconds) |
| 2025-02-28 04:36:46 +0100 | a_fantom | (~fantom@2.219.56.221) |
| 2025-02-28 04:35:42 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-02-28 04:25:13 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds) |
| 2025-02-28 04:20:20 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-02-28 04:20:16 +0100 | alp | (~alp@2001:861:8ca0:4940:58d8:cc89:9d90:c4b2) (Ping timeout: 268 seconds) |
| 2025-02-28 04:19:18 +0100 | weary-traveler | (~user@user/user363627) user363627 |
| 2025-02-28 04:16:52 +0100 | <Square2> | they* |
| 2025-02-28 04:16:43 +0100 | <Square2> | Yeah, that might be it and somewhat checks out what the wrote in the release notes |
| 2025-02-28 04:15:14 +0100 | <EvanR> | A might not know about stuff in C until after TH runs when it's too late |
| 2025-02-28 04:14:34 +0100 | <EvanR> | that makes more sense |
| 2025-02-28 04:12:10 +0100 | <Square2> | So this is my observation. If I have a .hs file. If I have 3 blocks of code in that file. part A, part B, part C. If part B is TH usage, the constraint solving between part A and C is broken. |
| 2025-02-28 04:09:47 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 268 seconds) |
| 2025-02-28 04:08:02 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 252 seconds) |
| 2025-02-28 04:04:57 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-02-28 04:03:44 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-02-28 04:03:37 +0100 | <Square2> | But, it seems it didn't. I need to provide an example to hope to get some meaningful input on this I realize. |
| 2025-02-28 04:02:54 +0100 | <Square2> | well, the question today wasn't about TH really. I just pasted the TH output in the problematic file and hoped it would solve itself. |
| 2025-02-28 04:02:15 +0100 | <monochrom> | deja vu? I thought that was explained and resolved yesterday. |
| 2025-02-28 04:00:19 +0100 | <geekosaur> | but TH is necessarily difficult as it has to be run during parsing |
| 2025-02-28 03:59:50 +0100 | <geekosaur> | ghc tightened some TH stage restrictions, IIRC |
| 2025-02-28 03:59:17 +0100 | <EvanR> | definitions can be in any order within the same file |
| 2025-02-28 03:58:44 +0100 | <Square2> | hehe... I guess I could word taht better. But i guess frustration hit. |
| 2025-02-28 03:58:24 +0100 | <EvanR> | say what |
| 2025-02-28 03:58:06 +0100 | <Square2> | It seems the contraint checker in ghc 9 has gotten a lot stricter? There is no way to relax it per file? Like all declarations needs to be in order. |
| 2025-02-28 03:57:54 +0100 | jathan | (~jathan@2607:1a00:0:19::2:1dc) (Quit: WeeChat 2.3) |
| 2025-02-28 03:53:49 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds) |
| 2025-02-28 03:52:38 +0100 | j1n37 | (~j1n37@user/j1n37) (Ping timeout: 252 seconds) |
| 2025-02-28 03:51:44 +0100 | j1n37- | (~j1n37@user/j1n37) j1n37 |
| 2025-02-28 03:51:10 +0100 | k_hachig_ | (~k_hachig@bras-base-toroon0247w-grc-123-70-29-50-103.dsl.bell.ca) (Ping timeout: 252 seconds) |
| 2025-02-28 03:49:36 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-02-28 03:44:42 +0100 | k_hachig_ | (~k_hachig@bras-base-toroon0247w-grc-123-70-29-50-103.dsl.bell.ca) k_hachig |
| 2025-02-28 03:39:08 +0100 | lockywolf | (~lockywolf@213.165.252.157) (Leaving) |
| 2025-02-28 03:38:49 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds) |
| 2025-02-28 03:36:03 +0100 | j1n37 | (~j1n37@user/j1n37) j1n37 |
| 2025-02-28 03:34:10 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-02-28 03:31:42 +0100 | euphores | (~SASL_euph@user/euphores) euphores |
| 2025-02-28 03:27:12 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) (Ping timeout: 264 seconds) |
| 2025-02-28 03:25:46 +0100 | euphores | (~SASL_euph@user/euphores) (Ping timeout: 265 seconds) |
| 2025-02-28 03:23:20 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds) |
| 2025-02-28 03:22:52 +0100 | k_hachig | (~k_hachig@bras-base-toroon0247w-grc-123-70-29-50-103.dsl.bell.ca) (Ping timeout: 265 seconds) |
| 2025-02-28 03:21:06 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 252 seconds) |