2025/03/30

Newest at the top

2025-03-30 13:32:03 +0200amishastra
2025-03-30 13:30:42 +0200amish(sid289983@user/amish) amish
2025-03-30 13:30:42 +0200amish(sid289983@id-289983.hampstead.irccloud.com) (Changing host)
2025-03-30 13:30:33 +0200astraamish
2025-03-30 13:25:33 +0200acidjnk(~acidjnk@p200300d6e71c4f61790abc3a16c69e44.dip0.t-ipconnect.de) (Ping timeout: 268 seconds)
2025-03-30 13:23:33 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-03-30 13:20:18 +0200connrs(~connrs@user/connrs) connrs
2025-03-30 13:20:10 +0200connrs(~connrs@user/connrs) (Remote host closed the connection)
2025-03-30 13:18:43 +0200 <haskellbridge> <thirdofmay18081814goya> hm what's the optic that will remove the elements of a list located at an even index? some combination using the enumeration "Iso' [a] [(Int, a)]" and something involving "traversed . filtered even", right?
2025-03-30 13:12:49 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds)
2025-03-30 13:11:07 +0200connrs(~connrs@user/connrs) connrs
2025-03-30 13:10:51 +0200connrs(~connrs@user/connrs) (Remote host closed the connection)
2025-03-30 13:10:21 +0200connrs(~connrs@user/connrs) connrs
2025-03-30 13:10:13 +0200connrs(~connrs@user/connrs) (Remote host closed the connection)
2025-03-30 13:07:47 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-03-30 13:01:24 +0200 <Rembane> thirdofmay18081814goya: No worries! :)
2025-03-30 13:01:16 +0200 <int-e> And Control.Monad.Error mimicked that after the MonadFail class was introduced.
2025-03-30 13:00:33 +0200 <int-e> `fail` used to be in `Monad` and the Monad instance for Either used to be instance Error e => Monad (Either e) where `Error` had a function to convert String into an e, which was used to implement `fail`.
2025-03-30 13:00:31 +0200 <haskellbridge> <thirdofmay18081814goya> @Rembane neat! didn't know about it, ty
2025-03-30 12:59:54 +0200hattckory(~hattckory@70.27.118.207) (Ping timeout: 260 seconds)
2025-03-30 12:59:26 +0200 <int-e> yes
2025-03-30 12:59:19 +0200 <Rembane> int-e: Ah, this has some history.
2025-03-30 12:59:03 +0200sprotte24(~sprotte24@p200300d16f1e0e006577a4ba097b8b9e.dip0.t-ipconnect.de) (Quit: Leaving)
2025-03-30 12:58:05 +0200 <int-e> Rembane: Well I used it before it was deprecated because it offered the behavior that Either had before the MonadFail proposal.
2025-03-30 12:56:57 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds)
2025-03-30 12:56:47 +0200 <Rembane> Was it a good MonadFail instance?
2025-03-30 12:56:39 +0200 <Rembane> That sounds potentially controversial. I never used ErrorT because of the deprecated message on top of the documentation of the module.
2025-03-30 12:54:30 +0200 <int-e> ExceptT e Foo a uses the MonadFail instance of Foo. ErrorT e Foo a was removed because it was deprecated in favor of ExceptT despite having a different MonadFail instance.
2025-03-30 12:54:10 +0200 <Rembane> Got it.
2025-03-30 12:53:42 +0200 <int-e> Either doesn't have a MonadFail instance
2025-03-30 12:51:59 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-03-30 12:49:09 +0200 <Rembane> I thought Either did that, what does it do instead?
2025-03-30 12:48:47 +0200 <[exa]> what's annoying on validation and either that neither of these provides the "just shortcircuit with errory error" behavior unless you write the MonadFail yourself
2025-03-30 12:48:35 +0200 <Rembane> [exa]: Yeah, it's usually better for inspiration than a clear definition. :D
2025-03-30 12:48:15 +0200sprotte24(~sprotte24@p200300d16f1e0e006577a4ba097b8b9e.dip0.t-ipconnect.de)
2025-03-30 12:47:40 +0200 <[exa]> absolutely not sure, just wanted to point out that the "opposite" is a very free definition :D
2025-03-30 12:47:11 +0200 <Rembane> [exa]: Bah, they don't actually exist. The closest I can get to them is Dual. What would Up and Down do?
2025-03-30 12:46:43 +0200pavonia(~user@user/siracusa) (Quit: Bye!)
2025-03-30 12:45:44 +0200 <Rembane> [exa]: I think we have some of those. They're usually Monoid/Semigroup newtypes.
2025-03-30 12:44:53 +0200 <[exa]> Rembane: so many opposites. Why don't we have a Up Down type?
2025-03-30 12:41:10 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-03-30 12:36:13 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-03-30 12:24:36 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds)
2025-03-30 12:15:49 +0200NewtonTrendy(~ubuntu@user/bopqod) (Quit: WeeChat 3.5)
2025-03-30 12:14:23 +0200polyphem(~rod@p4fc2c911.dip0.t-ipconnect.de) polyphem
2025-03-30 12:11:29 +0200Sgeo(~Sgeo@user/sgeo) (Read error: Connection reset by peer)
2025-03-30 11:59:42 +0200vgtw(~vgtw@user/vgtw) vgtw
2025-03-30 11:59:24 +0200vgtw(~vgtw@user/vgtw) (Ping timeout: 260 seconds)
2025-03-30 11:58:23 +0200hattckory(~hattckory@70.27.118.207)
2025-03-30 11:56:51 +0200ash3en(~Thunderbi@89.56.182.235) ash3en