Newest at the top
| 2024-10-26 21:36:29 +0200 | acidjnk_new | (~acidjnk@p200300d6e72cfb93adcc55b40ab8063a.dip0.t-ipconnect.de) acidjnk |
| 2024-10-26 21:36:23 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-10-26 21:32:55 +0200 | hgolden_ | (~hgolden@169.150.203.10) (Ping timeout: 252 seconds) |
| 2024-10-26 21:30:20 +0200 | hgolden__ | (~hgolden@169.150.203.23) hgolden |
| 2024-10-26 21:30:02 +0200 | acidjnk_new | (~acidjnk@p200300d6e72cfb938d9bba7e49be47ab.dip0.t-ipconnect.de) (Ping timeout: 272 seconds) |
| 2024-10-26 21:20:57 +0200 | LukeHoersten | (~LukeHoers@user/lukehoersten) LukeHoersten |
| 2024-10-26 21:20:24 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 246 seconds) |
| 2024-10-26 21:20:08 +0200 | <tomsmeding> | oof, an unqualified import of Data.Text is indeed unwise |
| 2024-10-26 21:18:27 +0200 | <geekosaur> | hm, at least some of the current list of trustees do hang out in #hackage so I'm doing some pings |
| 2024-10-26 21:16:54 +0200 | <tomsmeding> | don't know whether haskell-cafe or ghc-devs would have more success |
| 2024-10-26 21:16:19 +0200 | <tomsmeding> | ask the haskell-cafe mailing list? |
| 2024-10-26 21:15:42 +0200 | xal | (~xal@mx1.xal.systems) xal |
| 2024-10-26 21:15:36 +0200 | Sgeo | (~Sgeo@user/sgeo) Sgeo |
| 2024-10-26 21:15:26 +0200 | <geekosaur> | I already raised it in #hackage but nobody seems to be around and I think Hackage trustees don't hang out in either place |
| 2024-10-26 21:15:14 +0200 | xal | (~xal@mx1.xal.systems) (Quit: bye) |
| 2024-10-26 21:15:05 +0200 | <geekosaur> | that's ops issues |
| 2024-10-26 21:14:43 +0200 | <tomsmeding> | geekosaur: I'd expect that you should ask hackage admins; is that not #hackage-infrastructure or something? |
| 2024-10-26 21:13:45 +0200 | <geekosaur> | (so much for my plans to work on bignum=bsdnt this weekend; this just broke cabal's CI) |
| 2024-10-26 21:13:30 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-10-26 21:13:24 +0200 | emmanuelux | (~emmanuelu@user/emmanuelux) emmanuelux |
| 2024-10-26 21:11:23 +0200 | Katarushisu | (~Katarushi@finc-20-b2-v4wan-169598-cust1799.vm7.cable.virginm.net) Katarushisu |
| 2024-10-26 21:11:07 +0200 | <geekosaur> | looks like the just released `text-2.1.2` breaks `parsers`. I just filed a bug because minor updates shouldn't do that. how do I request an emergency revision on `parsers` in the meantime? |
| 2024-10-26 21:06:57 +0200 | __monty__ | (~toonn@user/toonn) (Quit: leaving) |
| 2024-10-26 21:02:36 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds) |
| 2024-10-26 21:02:00 +0200 | briandaed | (~root@185.234.210.211) (Remote host closed the connection) |
| 2024-10-26 21:00:39 +0200 | caconym | (~caconym@user/caconym) caconym |
| 2024-10-26 21:00:01 +0200 | caconym | (~caconym@user/caconym) (Quit: bye) |
| 2024-10-26 20:59:38 +0200 | EvanR | (~EvanR@user/evanr) (Quit: Leaving) |
| 2024-10-26 20:58:07 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-10-26 20:48:16 +0200 | <tomsmeding> | (they just renamed actual data constructors with more specific types; now I'm just using the more general constructors in place of the renamed aliases) |
| 2024-10-26 20:47:17 +0200 | <tomsmeding> | so ghc is happy now, and I have code that is almost as readable |
| 2024-10-26 20:47:06 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds) |
| 2024-10-26 20:46:58 +0200 | <tomsmeding> | no, the pattern synonyms were simple enough that I could just inline their definitions at their usage sites |
| 2024-10-26 20:46:31 +0200 | <monochrom> | So now you are just looking for a way to turn off another warning, namely that of inexhaustiveness? |
| 2024-10-26 20:45:48 +0200 | <monochrom> | haha |
| 2024-10-26 20:44:11 +0200 | <tomsmeding> | turns out the pattern synonyms were not really pulling their weight and I could just remove them altogether :) |
| 2024-10-26 20:43:54 +0200 | <tomsmeding> | ah, I worked around it |
| 2024-10-26 20:42:45 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-10-26 20:40:50 +0200 | <tomsmeding> | (as I've thought many times before: GHC should have vastly many more diagnostics/extensions/etc. that can be regulated on the binding level instead of on the module level) |
| 2024-10-26 20:38:20 +0200 | <tomsmeding> | I'd rather not add -Wno-unused-top-binds to the entire module, but I also cannot remove this unused top-level binding! What do? |
| 2024-10-26 20:37:47 +0200 | <tomsmeding> | (this is possible because the pattern synonyms both have some _provided_ constraints, and the unused one provides a constraint that is contradictory with the other info in the function in question, so it is impossible.) |
| 2024-10-26 20:37:10 +0200 | <tomsmeding> | I have a somewhat peculiar issue. I have two pattern synonyms in a module that are together in a COMPLETE pragma; they are only for internal use in the module. But I end up using only one of them, so I get a warning that the other is unused. But I cannot remove it, because then I would also have to remove the COMPLETE pragma, and I was using it to prove to GHC that some functions are exhaustive! |
| 2024-10-26 20:35:30 +0200 | tromp | (~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) |
| 2024-10-26 20:33:53 +0200 | Katarushisu | (~Katarushi@finc-20-b2-v4wan-169598-cust1799.vm7.cable.virginm.net) (Quit: The Lounge - https://thelounge.chat) |
| 2024-10-26 20:29:30 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds) |
| 2024-10-26 20:28:37 +0200 | <tomsmeding> | druchan: to summarise: the cross-compilation story with GHC is not as good as with Go |
| 2024-10-26 20:26:35 +0200 | chexum | (~quassel@gateway/tor-sasl/chexum) chexum |
| 2024-10-26 20:26:24 +0200 | chexum | (~quassel@gateway/tor-sasl/chexum) (Remote host closed the connection) |
| 2024-10-26 20:25:02 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-10-26 20:14:08 +0200 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 245 seconds) |