2025/05/05

Newest at the top

2025-05-05 23:42:52 +0200 <EvanR> you're a 3 > haskell programmer now
2025-05-05 23:42:41 +0200fp(~Thunderbi@hof1.kyla.fi) (Ping timeout: 252 seconds)
2025-05-05 23:42:35 +0200 <lambdabot> forall k (cat :: k -> k -> *) (a :: k) (b :: k) (c :: k). Category cat => cat a b -> cat b c -> cat a c
2025-05-05 23:42:34 +0200 <EvanR> :t (>>>)
2025-05-05 23:35:09 +0200tolgo(~Thunderbi@199.115.144.130) (Quit: tolgo)
2025-05-05 23:32:40 +0200__monty__(~toonn@user/toonn) (Quit: leaving)
2025-05-05 23:30:21 +0200 <monochrom> Don't worry, (>>>) is merely Category so we're OK with it. :)
2025-05-05 23:28:30 +0200 <haskellbridge> <Liamzee> "did you just disguise point free code as a verticalized arrow-operator chain?"
2025-05-05 23:28:22 +0200tolgo(~Thunderbi@199.115.144.130)
2025-05-05 23:28:06 +0200 <haskellbridge> <Liamzee> i abuse >>> all the time
2025-05-05 23:28:04 +0200Guest12(~Guest12@82.148.184.53)
2025-05-05 23:28:01 +0200 <haskellbridge> <Liamzee> tomsmeding: arrow in general is about the arrow classes, no?
2025-05-05 23:26:24 +0200greber(~greber@82.148.184.53)
2025-05-05 23:14:34 +0200zmt01(~zmt00@user/zmt00) (Ping timeout: 245 seconds)
2025-05-05 23:11:22 +0200swamp_(~zmt00@user/zmt00) zmt00
2025-05-05 23:10:25 +0200j1n37-(~j1n37@user/j1n37) (Ping timeout: 252 seconds)
2025-05-05 23:09:42 +0200Square(~Square@user/square) Square
2025-05-05 23:09:29 +0200j1n37(~j1n37@user/j1n37) j1n37
2025-05-05 23:02:43 +0200ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 252 seconds)
2025-05-05 22:57:09 +0200ttybitnik(~ttybitnik@user/wolper) ttybitnik
2025-05-05 22:46:44 +0200takuan(~takuan@d8D86B601.access.telenet.be) (Remote host closed the connection)
2025-05-05 22:39:46 +0200Guest2892jinsun
2025-05-05 22:39:45 +0200Guest2892(jinsun@user/jinsun) jinsun
2025-05-05 22:39:45 +0200Guest2892(jinsun@here.and.ready-to.party) (Changing host)
2025-05-05 22:38:05 +0200jinsunGuest2892
2025-05-05 22:37:42 +0200jinsun(jinsun@here.and.ready-to.party)
2025-05-05 22:30:02 +0200xacktm(xacktm@user/xacktm) xacktm
2025-05-05 22:27:30 +0200aljazmc(~aljazmc@user/aljazmc) (Quit: Leaving)
2025-05-05 22:25:45 +0200jespada(~jespada@r179-25-149-142.dialup.adsl.anteldata.net.uy) jespada
2025-05-05 22:24:42 +0200jespada_(~jespada@r179-25-149-142.dialup.adsl.anteldata.net.uy) (Quit: My Mac has gone to sleep. ZZZzzz…)
2025-05-05 22:17:05 +0200prdak(~Thunderbi@user/prdak) (Ping timeout: 265 seconds)
2025-05-05 22:15:31 +0200euleritian(~euleritia@dynamic-176-000-054-130.176.0.pool.telefonica.de)
2025-05-05 22:14:16 +0200euleritian(~euleritia@ip5f5ad197.dynamic.kabel-deutschland.de) (Ping timeout: 252 seconds)
2025-05-05 22:12:32 +0200prdak(~Thunderbi@user/prdak) prdak
2025-05-05 22:03:49 +0200jinsun(jinsun@user/jinsun) (Ping timeout: 272 seconds)
2025-05-05 22:01:57 +0200vanishingideal(~vanishing@user/vanishingideal) vanishingideal
2025-05-05 21:51:48 +0200xacktm(xacktm@user/xacktm) (Quit: fBNC - https://bnc4free.com)
2025-05-05 21:48:53 +0200fp(~Thunderbi@hof1.kyla.fi) fp
2025-05-05 21:43:08 +0200ljdarj(~Thunderbi@user/ljdarj) ljdarj
2025-05-05 21:40:38 +0200pavonia(~user@user/siracusa) siracusa
2025-05-05 21:35:00 +0200DigitteknohippieDigit
2025-05-05 21:34:38 +0200weary-traveler(~user@user/user363627) user363627
2025-05-05 21:25:52 +0200L29Ah(~L29Ah@wikipedia/L29Ah) L29Ah
2025-05-05 21:24:11 +0200 <c_wraith> It's abstracting over the wrong (for most use cases) thing, so it needs more and more pieces to cover common cases
2025-05-05 21:23:33 +0200 <c_wraith> Where this difference really pays off is that Bifunctor's first also works with Either, but if you're using Arrow you need to switch to left instead
2025-05-05 21:20:58 +0200 <c_wraith> Or really, functions on values that can be tupled.
2025-05-05 21:19:28 +0200 <c_wraith> Arrow is about abstracting over functions on tuples
2025-05-05 21:18:55 +0200 <c_wraith> Also, Arrow is a weird fit. like Bifunctor is very directly just giving you access to a covariant functor on two type variables instead of one. That's its whole purpose.
2025-05-05 21:16:41 +0200 <c_wraith> that's a corollary to the principle of least power, at least for abstract interfaces. The more things that can implement an interface, the less powerful it is.
2025-05-05 21:15:26 +0200 <tomsmeding> I guess