2024/10/26

Newest at the top

2024-10-26 22:20:28 +0200alp(~alp@2001:861:e3d6:8f80:f680:7e0c:c173:50ab)
2024-10-26 22:14:13 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 248 seconds)
2024-10-26 22:13:06 +0200druchan(uid567859@id-567859.lymington.irccloud.com) (Quit: Connection closed for inactivity)
2024-10-26 22:09:54 +0200euphores(~SASL_euph@user/euphores) euphores
2024-10-26 22:09:51 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-10-26 22:03:21 +0200euphores(~SASL_euph@user/euphores) (Ping timeout: 252 seconds)
2024-10-26 22:01:06 +0200sadmax(~user@64.130.91.66)
2024-10-26 21:59:45 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 276 seconds)
2024-10-26 21:59:09 +0200Everything(~Everythin@static.208.206.21.65.clients.your-server.de) (Quit: leaving)
2024-10-26 21:54:29 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-10-26 21:48:11 +0200ljdarj1(~Thunderbi@user/ljdarj) (Ping timeout: 265 seconds)
2024-10-26 21:45:22 +0200ljdarj(~Thunderbi@user/ljdarj) ljdarj
2024-10-26 21:44:49 +0200ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 260 seconds)
2024-10-26 21:43:47 +0200ljdarj1(~Thunderbi@user/ljdarj) ljdarj
2024-10-26 21:41:05 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 248 seconds)
2024-10-26 21:36:29 +0200acidjnk_new(~acidjnk@p200300d6e72cfb93adcc55b40ab8063a.dip0.t-ipconnect.de) acidjnk
2024-10-26 21:36:23 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-10-26 21:32:55 +0200hgolden_(~hgolden@169.150.203.10) (Ping timeout: 252 seconds)
2024-10-26 21:30:20 +0200hgolden__(~hgolden@169.150.203.23) hgolden
2024-10-26 21:30:02 +0200acidjnk_new(~acidjnk@p200300d6e72cfb938d9bba7e49be47ab.dip0.t-ipconnect.de) (Ping timeout: 272 seconds)
2024-10-26 21:20:57 +0200LukeHoersten(~LukeHoers@user/lukehoersten) LukeHoersten
2024-10-26 21:20:24 +0200merijn(~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 +0200xal(~xal@mx1.xal.systems) xal
2024-10-26 21:15:36 +0200Sgeo(~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 +0200xal(~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 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-10-26 21:13:24 +0200emmanuelux(~emmanuelu@user/emmanuelux) emmanuelux
2024-10-26 21:11:23 +0200Katarushisu(~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 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds)
2024-10-26 21:02:00 +0200briandaed(~root@185.234.210.211) (Remote host closed the connection)
2024-10-26 21:00:39 +0200caconym(~caconym@user/caconym) caconym
2024-10-26 21:00:01 +0200caconym(~caconym@user/caconym) (Quit: bye)
2024-10-26 20:59:38 +0200EvanR(~EvanR@user/evanr) (Quit: Leaving)
2024-10-26 20:58:07 +0200merijn(~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 +0200merijn(~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