2024/12/29

Newest at the top

2024-12-29 02:18:58 +0100sprotte24(~sprotte24@p200300d16f0bfe00711e65c2b30202f1.dip0.t-ipconnect.de) (Read error: Connection reset by peer)
2024-12-29 02:17:48 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-29 02:08:03 +0100foul_owl(~kerry@193.42.0.124) foul_owl
2024-12-29 02:06:29 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 248 seconds)
2024-12-29 02:01:45 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-29 01:54:26 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds)
2024-12-29 01:53:49 +0100foul_owl(~kerry@174-21-81-201.tukw.qwest.net) (Ping timeout: 252 seconds)
2024-12-29 01:49:49 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-29 01:43:41 +0100Everything(~Everythin@195.138.86.118) (Quit: leaving)
2024-12-29 01:42:13 +0100Tuplanolla(~Tuplanoll@91-159-69-59.elisa-laajakaista.fi) (Quit: Leaving.)
2024-12-29 01:42:11 +0100mhatta(~mhatta@www21123ui.sakura.ne.jp)
2024-12-29 01:42:05 +0100 <ncf> there's some motivation here https://stackoverflow.com/questions/28690448/what-is-indexed-monad
2024-12-29 01:40:41 +0100 <ncf> are you thinking of exofunctors or something
2024-12-29 01:40:15 +0100 <geekosaur> maybe I'm completely confused, that was what I thought (part of) the point of it was
2024-12-29 01:38:30 +0100 <ncf> geekosaur: i don't think Set is an indexed monad?
2024-12-29 01:37:53 +0100mhatta(~mhatta@www21123ui.sakura.ne.jp) (Remote host closed the connection)
2024-12-29 01:36:59 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds)
2024-12-29 01:32:26 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-29 01:27:21 +0100wootehfoot(~wootehfoo@user/wootehfoot) (Quit: pillow time)
2024-12-29 01:25:43 +0100 <hololeap> it reminds me of (.|) :: Monad m => ConduitT a b m () -> ConduitT b c m r -> ConduitT a c m r
2024-12-29 01:19:36 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 276 seconds)
2024-12-29 01:18:37 +0100ljdarj1ljdarj
2024-12-29 01:18:37 +0100ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 265 seconds)
2024-12-29 01:16:18 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Client Quit)
2024-12-29 01:15:48 +0100ljdarj1(~Thunderbi@user/ljdarj) ljdarj
2024-12-29 01:15:16 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2024-12-29 01:12:08 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-29 01:11:01 +0100alp(~alp@128-79-174-146.hfc.dyn.abo.bbox.fr) (Ping timeout: 248 seconds)
2024-12-29 01:10:48 +0100todi(~todi@p57803331.dip0.t-ipconnect.de) (Ping timeout: 252 seconds)
2024-12-29 01:09:58 +0100todi1(~todi@p57803331.dip0.t-ipconnect.de)
2024-12-29 01:08:22 +0100 <geekosaur> and I think mathematically (but sadly not in Haskell's type system) if i == j then it should reduce to a normal non-indexed monad
2024-12-29 01:07:45 +0100 <geekosaur> more generally, a would be Map k v, b would be Map k' v', i is k and j is k'
2024-12-29 01:06:39 +0100iteratee(~kyle@162.218.222.207) (Remote host closed the connection)
2024-12-29 01:05:17 +0100 <haskellbridge> <thirdofmay18081814goya> hm right
2024-12-29 01:02:54 +0100 <geekosaur> (meaning i, j, k are the key types since those specify the Ord instances, again AIUI)
2024-12-29 01:02:18 +0100 <geekosaur> (since one of the uses of indexed monads is to allow things like an indexed monad instance for Set, which normally isn't possible because changing the key type alters the structure to reflect a different Ord instance. AIUI at least)
2024-12-29 01:01:59 +0100gentauro(~gentauro@user/gentauro) gentauro
2024-12-29 01:01:27 +0100lol_jcarpenter2
2024-12-29 01:00:36 +0100foul_owl(~kerry@174-21-81-201.tukw.qwest.net) foul_owl
2024-12-29 01:00:21 +0100 <geekosaur> so it tracks the original and final Ord instances
2024-12-29 00:59:55 +0100 <geekosaur> think a and b having different Ord instances
2024-12-29 00:59:55 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds)
2024-12-29 00:56:00 +0100gentauro(~gentauro@user/gentauro) (Read error: Connection reset by peer)
2024-12-29 00:55:18 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-29 00:54:22 +0100 <haskellbridge> <thirdofmay18081814goya> you'll want two indexed*
2024-12-29 00:54:10 +0100 <haskellbridge> <thirdofmay18081814goya> hm but maybe you'll two indexes if you're mapping from lists of length n to lists of length m?
2024-12-29 00:53:11 +0100 <haskellbridge> <thirdofmay18081814goya> the usage of one index is understandable, e.g. the type of lists with a given length
2024-12-29 00:52:35 +0100 <haskellbridge> <thirdofmay18081814goya> next question is... why two indexes?
2024-12-29 00:48:26 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds)
2024-12-29 00:47:51 +0100 <haskellbridge> <thirdofmay18081814goya> was reading that wrong