2026/02/15

Newest at the top

2026-02-15 21:30:31 +0100 <larsivi> exa: In the next step I want to pattern match op1:op2, how does that work with a pair?
2026-02-15 21:29:28 +0100 <[exa]> (btw you could do something like (+1):[(+0)] to make it work with : , but that doesn't quite look like what you'd want to do)
2026-02-15 21:27:43 +0100 <lambdabot> Num a => [a -> a]
2026-02-15 21:27:42 +0100 <[exa]> :t [(+1),(+0)]
2026-02-15 21:27:37 +0100 <lambdabot> (Num a1, Num a2) => (a1 -> a1, a2 -> a2)
2026-02-15 21:27:37 +0100 <[exa]> :t ((+1),(+0))
2026-02-15 21:27:11 +0100 <[exa]> or Left ((+1),(+0)) if you're sure there's always an exact couple
2026-02-15 21:26:53 +0100 <[exa]> larsivi: use Left [(+1),(+0)]? the issue is likely the type of (:), it requires a list on the right
2026-02-15 21:25:45 +0100 <larsivi> Still learning Haskell here, trying some stuff where I want to return a couple of operations in Left and something else in Right, so like this: Left ((+1):(+0)) However, it fails since +1 and +0 are not the same type. Is there some way yo make this into a more generic type? (in addition to addition, I also have subtractions)
2026-02-15 21:24:04 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds)
2026-02-15 21:23:44 +0100 <monochrom> Coding OO in Haskell becomes annoying once you start subclassing. (Too much boilerplate.)
2026-02-15 21:21:59 +0100notzmv(~umar@user/notzmv) (Ping timeout: 252 seconds)
2026-02-15 21:19:06 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-02-15 21:18:41 +0100spew(~spew@user/spew) (Ping timeout: 252 seconds)
2026-02-15 21:16:00 +0100wickedjargon(~user@24.83.46.194) (Remote host closed the connection)
2026-02-15 21:15:02 +0100drlkf(~drlkf@chat-1.drlkf.net) (Quit: WeeChat 3.8)
2026-02-15 21:14:31 +0100spew(~spew@user/spew) spew
2026-02-15 21:14:28 +0100notzmv(~umar@user/notzmv) notzmv
2026-02-15 21:08:43 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds)
2026-02-15 21:06:28 +0100 <int-e> (you can always play dirty)
2026-02-15 21:06:17 +0100 <lambdabot> 42
2026-02-15 21:06:16 +0100 <int-e> > let clаss = 42 in clаss
2026-02-15 21:05:35 +0100 <geekosaur> I think there's an unimplemented-as-yet proposal for keywords and such to be usable as fields disambiguated by the overloaded dot
2026-02-15 21:03:23 +0100 <EvanR> doesn't work, though it would see that would avoid syntactic collisions
2026-02-15 21:03:20 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-02-15 21:03:17 +0100spew(~spew@user/spew) (Ping timeout: 252 seconds)
2026-02-15 21:01:58 +0100 <EvanR> *attempts to get around it with NoFieldSelectors
2026-02-15 21:01:23 +0100 <int-e> trait carefully, or something
2026-02-15 21:00:58 +0100 <EvanR> and jreicher is trying to claim we're not OOP xD
2026-02-15 21:00:20 +0100KindFoxo(~KindFoxo@user/KindoFoxo) KindoFoxo
2026-02-15 21:00:18 +0100 <int-e> it is a keyword
2026-02-15 20:59:55 +0100 <EvanR> wow... you can't use the field name "class" ?
2026-02-15 20:52:17 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2026-02-15 20:50:56 +0100emmanuelux(~em@user/emmanuelux) emmanuelux
2026-02-15 20:49:50 +0100emmanuelux(~em@user/emmanuelux) (Quit: bye)
2026-02-15 20:47:33 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-02-15 20:45:54 +0100Lord_of_Life_Lord_of_Life
2026-02-15 20:45:41 +0100Lord_of_Life(~Lord@user/lord-of-life/x-2819915) (Ping timeout: 252 seconds)
2026-02-15 20:44:32 +0100Lord_of_Life_(~Lord@user/lord-of-life/x-2819915) Lord_of_Life
2026-02-15 20:37:59 +0100prdak(~Thunderbi@user/prdak) (Ping timeout: 252 seconds)
2026-02-15 20:36:53 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2026-02-15 20:35:05 +0100oats(~oats@user/oats) oats
2026-02-15 20:34:49 +0100oats(~oats@user/oats) (Read error: Connection reset by peer)
2026-02-15 20:34:35 +0100 <EvanR> I don't envy someone with a dog in that race xD
2026-02-15 20:34:12 +0100 <EvanR> attempt to define the terminology jargon "once and for all" is boiling an ocean
2026-02-15 20:33:28 +0100 <EvanR> jreicher, this is arguably the main issue with OOP as a subject, that people can't agree on what it entails. So in the end it's just easier to discuss the subject matter itself
2026-02-15 20:33:14 +0100prdak(~Thunderbi@user/prdak) prdak
2026-02-15 20:32:07 +0100EvanR(~EvanR@user/evanr) EvanR
2026-02-15 20:32:00 +0100emmanuelux(~em@user/emmanuelux) emmanuelux
2026-02-15 20:31:31 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn