2024/12/23

Newest at the top

2024-12-23 10:45:18 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 276 seconds)
2024-12-23 10:40:33 +0100Guest33(~Guest33@2001:1600:13:101::60e) (Client Quit)
2024-12-23 10:40:24 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-23 10:38:50 +0100Guest33(~Guest33@2001:1600:13:101::60e)
2024-12-23 10:38:19 +0100__monty__(~toonn@user/toonn) toonn
2024-12-23 10:36:38 +0100lortabac(~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4) lortabac
2024-12-23 10:35:28 +0100manwithluck(~manwithlu@194.177.28.164) manwithluck
2024-12-23 10:34:54 +0100xff0x(~xff0x@p3704193-ipxg12201sapodori.hokkaido.ocn.ne.jp) (Ping timeout: 272 seconds)
2024-12-23 10:32:33 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 248 seconds)
2024-12-23 10:28:13 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-23 10:24:40 +0100peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 260 seconds)
2024-12-23 10:23:38 +0100Guest33(~Guest33@2001:1600:13:101::60e) (Quit: Client closed)
2024-12-23 10:19:37 +0100 <Guest33> Naked cont and naked state apparently can't have an instance, and it's probably a good thing due to overlapping instances
2024-12-23 10:18:55 +0100 <Guest33> The curiosity is more about naked reader having an instance in base
2024-12-23 10:18:38 +0100 <int-e> Sure.
2024-12-23 10:18:30 +0100 <Guest33> I mean if you go to newtype, just get Control.Monad.Trans and call it a day
2024-12-23 10:17:50 +0100 <int-e> Anyway, use a newtype and that solves this problem. You can think of naming that newtype in your code as hinting to the compiler to introduce the right type-level lambda if you like.
2024-12-23 10:17:28 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds)
2024-12-23 10:16:54 +0100 <int-e> But that's not what you'd want for Functor.
2024-12-23 10:16:53 +0100 <Guest33> Without newtypes of course, but that's just ContT identity and StateT identity
2024-12-23 10:16:29 +0100 <int-e> right. Well, I suppose you can try instance r ~ s => Foo ((a -> r) -> s)
2024-12-23 10:15:25 +0100 <Guest33> So there's no way to create an instance for (a -> r) -> r and s -> (s,a), right?
2024-12-23 10:13:37 +0100 <int-e> This would amount to a type-level lambda which we don't have.
2024-12-23 10:13:25 +0100 <Guest33> I know, that's what I'm asking about
2024-12-23 10:12:49 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-23 10:12:40 +0100 <int-e> you can't even match that instance head
2024-12-23 10:12:27 +0100 <Guest33> And honestly it'd result in overlapping instances, so...
2024-12-23 10:10:51 +0100 <Guest33> Or for that matter, type State s a...
2024-12-23 10:04:01 +0100 <Guest33> instance Functor (Cont r)
2024-12-23 10:03:39 +0100 <Guest33> type Cont r a = (a -> r) -> r
2024-12-23 10:02:57 +0100 <Guest33> Assume you can type it properly:
2024-12-23 10:02:42 +0100 <Guest33> Hi, is there a way to produce a native cont monad with just function arrows?
2024-12-23 10:02:36 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 272 seconds)
2024-12-23 10:02:09 +0100Guest33(~Guest33@2001:1600:13:101::60e)
2024-12-23 10:00:29 +0100tnt2tnt1
2024-12-23 10:00:29 +0100tnt1(~Thunderbi@user/tnt1) (Ping timeout: 252 seconds)
2024-12-23 09:59:31 +0100dsrt^(~dsrt@c-98-242-74-66.hsd1.ga.comcast.net) (Ping timeout: 252 seconds)
2024-12-23 09:59:09 +0100tnt2(~Thunderbi@user/tnt1) tnt1
2024-12-23 09:57:25 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-23 09:54:48 +0100acidjnk_new(~acidjnk@p200300d6e7283f25e9e9d221c37061e3.dip0.t-ipconnect.de) acidjnk
2024-12-23 09:46:13 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 248 seconds)
2024-12-23 09:43:04 +0100hc(~hc@mail.hce.li) (Remote host closed the connection)
2024-12-23 09:39:23 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-23 09:38:45 +0100youthlic(~Thunderbi@user/youthlic) (Quit: youthlic)
2024-12-23 09:29:15 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 276 seconds)
2024-12-23 09:24:32 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-23 09:13:22 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 244 seconds)
2024-12-23 09:09:09 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-23 09:08:39 +0100mari-estel(~mari-este@user/mari-estel) (Ping timeout: 260 seconds)
2024-12-23 09:08:33 +0100bheesham(3aa22d8375@2a03:6000:1812:100::e40) bheesham