2025/10/18

Newest at the top

2025-10-18 23:04:58 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds)
2025-10-18 23:04:21 +0200humasect(~humasect@dyn-192-249-132-90.nexicom.net) (Quit: Leaving...)
2025-10-18 23:00:15 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-18 22:51:37 +0200jmcantrell(~weechat@user/jmcantrell) (Ping timeout: 264 seconds)
2025-10-18 22:49:23 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds)
2025-10-18 22:45:33 +0200pavonia(~user@user/siracusa) siracusa
2025-10-18 22:44:49 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-18 22:43:49 +0200fgarciafgidim
2025-10-18 22:43:19 +0200Zemy(~Zemy@2600:100c:b0a7:4bfb:cc4d:4cff:fea8:fd90) (Ping timeout: 246 seconds)
2025-10-18 22:42:39 +0200fgarcia(~lei@user/fgarcia) fgarcia
2025-10-18 22:41:58 +0200fgidim(~lei@user/fgarcia) (Quit: Remote host closed the connection)
2025-10-18 22:40:11 +0200Everything(~Everythin@46.96.48.125) (Quit: leaving)
2025-10-18 22:39:43 +0200Zemy_(~Zemy@72.178.108.235)
2025-10-18 22:39:09 +0200Zemy_(~Zemy@72.178.108.235) (Read error: Connection reset by peer)
2025-10-18 22:39:08 +0200Zemy(~Zemy@2600:100c:b0a7:4bfb:cc4d:4cff:fea8:fd90)
2025-10-18 22:37:34 +0200 <EvanR> yes... nevermind that. But I do see GHC warns that AllowAmbiguousTypes may not interact nice with RankN
2025-10-18 22:34:27 +0200Zemy(~Zemy@2600:100c:b0a7:4bfb:24c8:fcff:fe1d:80e8) (Read error: Connection reset by peer)
2025-10-18 22:34:02 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds)
2025-10-18 22:33:33 +0200 <mreh> wouldn't you need to turn on OverlappingIstances too for that to fail?
2025-10-18 22:32:47 +0200 <EvanR> if you get an instance you know it was the right one for that type
2025-10-18 22:32:11 +0200 <EvanR> doesn't that cripple the entire cool part of type classes
2025-10-18 22:32:02 +0200Zemy_(~Zemy@72.178.108.235)
2025-10-18 22:31:46 +0200 <mreh> is there any downside to AllowAmbiguousTypes project wide?
2025-10-18 22:31:45 +0200morj(~morj@user/morj) (Quit: Konversation terminated!)
2025-10-18 22:31:28 +0200Zemy_(~Zemy@72.178.108.235) (Read error: Connection reset by peer)
2025-10-18 22:31:27 +0200Zemy(~Zemy@2600:100c:b0a7:4bfb:24c8:fcff:fe1d:80e8)
2025-10-18 22:29:32 +0200 <mreh> monochrom: it's pretty easy to translate to that form, and you only need AllowAmbiguousTypes on the file with the Class in
2025-10-18 22:29:03 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-18 22:28:44 +0200 <monochrom> Yeah the extreme way requires AllowAmbiguousTypes too.
2025-10-18 22:28:15 +0200 <monochrom> whodunit
2025-10-18 22:27:13 +0200 <mreh> I have so many Arrows that I need from some instance, which I don't always use to compute an actual value, so I'm always feeding undefined into those too
2025-10-18 22:22:27 +0200Zemy(~Zemy@2600:100c:b0a7:4bfb:f0d2:72ff:fe86:260e) (Ping timeout: 260 seconds)
2025-10-18 22:20:14 +0200Zemy_(~Zemy@72.178.108.235)
2025-10-18 22:19:41 +0200jreicher(~user@user/jreicher) (Quit: In transit)
2025-10-18 22:18:13 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds)
2025-10-18 22:16:31 +0200 <EvanR> ["a string"]
2025-10-18 22:16:29 +0200 <mreh> morj: that's funny
2025-10-18 22:16:28 +0200 <EvanR> whodis
2025-10-18 22:16:20 +0200 <EvanR> knock knock
2025-10-18 22:16:01 +0200 <morj> As a fun bonus, you can also do like `whodis ["a string"]`, which gives you the instance for the string
2025-10-18 22:15:24 +0200 <morj> Then this works with Proxy from base, or anything else the user has defined themselves
2025-10-18 22:15:23 +0200 <mreh> don't you also have to turn on AllowAmbiguousTypes?
2025-10-18 22:14:49 +0200 <morj> If you want to be fancy, you can also use an abstract proxy type: class Who a where whodis :: forall (proxy :: Type -> Type). proxy a -> String
2025-10-18 22:14:15 +0200 <mreh> I've already got it turned on, so I might start using that instead
2025-10-18 22:14:14 +0200morj(~morj@user/morj) morj
2025-10-18 22:13:46 +0200 <mreh> monochrom: that's a nice use of type applications I hadn't thought of
2025-10-18 22:13:17 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-18 22:12:07 +0200humasect(~humasect@dyn-192-249-132-90.nexicom.net)
2025-10-18 22:11:18 +0200jmcantrell(~weechat@user/jmcantrell) jmcantrell
2025-10-18 22:09:08 +0200forell(~forell@user/forell) forell