2025/10/14

Newest at the top

2025-10-14 19:46:01 +0200 <haskellbridge> <sm> I haven't been in those channels much.. are they active / working pretty well ?
2025-10-14 19:45:21 +0200vanishingideal(~vanishing@user/vanishingideal) vanishingideal
2025-10-14 19:44:39 +0200 <ski> with a more abstract/technical/theoretical conversation, going on for a longer time period, and there being other extant conversation threads, i often suggest #haskell-overflow or #haskell-in-depth
2025-10-14 19:44:29 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds)
2025-10-14 19:43:26 +0200tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net) tzh
2025-10-14 19:43:15 +0200vanishingideal(~vanishing@user/vanishingideal) (Ping timeout: 245 seconds)
2025-10-14 19:39:34 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-14 19:36:18 +0200gustrb(~gustrb@191.243.134.87) (Quit: gustrb)
2025-10-14 19:33:44 +0200Inline(~inlinE@ip-178-202-059-161.um47.pools.vodafone-ip.de) (Ping timeout: 256 seconds)
2025-10-14 19:33:35 +0200wootehfoot(~wootehfoo@user/wootehfoot) wootehfoot
2025-10-14 19:29:03 +0200weary-traveler(~user@user/user363627) user363627
2025-10-14 19:28:37 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds)
2025-10-14 19:27:29 +0200 <haskellbridge> <sm> I think it's in the nature of the language and the community that this tends to happen. There's a wider range of interests and discussion than say php or js. And also a greater need for careful coaching/mentoring than in those languages.
2025-10-14 19:25:36 +0200Square(~Square4@user/square) Square
2025-10-14 19:24:55 +0200Square3(~Square@user/square) Square
2025-10-14 19:23:46 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-14 19:23:03 +0200 <haskellbridge> <sm> #haskell-beginners was another attempt to separate the streams of new learners and deep divers. Also #Haskell matrix room has a bit less of this tendency I think
2025-10-14 19:21:01 +0200nogloff(uid464985@id-464985.tinside.irccloud.com)
2025-10-14 19:17:39 +0200Shark8(~Shark8@c-174-56-102-109.hsd1.nm.comcast.net)
2025-10-14 19:16:45 +0200Shark8(~Shark8@c-174-56-102-109.hsd1.nm.comcast.net) (Read error: Connection reset by peer)
2025-10-14 19:15:45 +0200Googulator60(~Googulato@2a01-036d-0106-03fa-dc7a-fb6e-71bb-aaf0.pool6.digikabel.hu)
2025-10-14 19:15:39 +0200Googulator3(~Googulato@2a01-036d-0106-03fa-dc7a-fb6e-71bb-aaf0.pool6.digikabel.hu) (Quit: Client closed)
2025-10-14 19:13:51 +0200haltsolver(~cmo@2604:3d09:207f:8000::d1dc)
2025-10-14 19:11:52 +0200gustrb(~gustrb@191.243.134.87)
2025-10-14 19:03:41 +0200gustrb(~gustrb@191.243.134.87) (Ping timeout: 256 seconds)
2025-10-14 19:01:39 +0200Zemy(~Zemy@syn-076-184-041-021.res.spectrum.com) (Ping timeout: 252 seconds)
2025-10-14 18:58:31 +0200mari-estel(~mari-este@user/mari-estel) (Remote host closed the connection)
2025-10-14 18:57:17 +0200peterbecich(~Thunderbi@syn-172-222-148-214.res.spectrum.com) (Ping timeout: 260 seconds)
2025-10-14 18:56:19 +0200 <ski> (just writing down the things i thought of, before i forget them again)
2025-10-14 18:55:48 +0200 <ski> right, that's fine
2025-10-14 18:55:21 +0200 <Tri> ski, I'm working right now so I haven't been able to parse all your suggestions, I will read it later. Thank you
2025-10-14 18:53:25 +0200Core7083(~Zemy@2600:100c:b0a0:3fd9:b093:6aff:fe5f:f77f) (Ping timeout: 246 seconds)
2025-10-14 18:52:40 +0200chele(~chele@user/chele) (Remote host closed the connection)
2025-10-14 18:52:24 +0200 <ski> Tri : do you see how to use `all' to avoid the matching on `Just' ?
2025-10-14 18:51:31 +0200bitdex(~bitdex@gateway/tor-sasl/bitdex) (Quit: = "")
2025-10-14 18:51:30 +0200EvanR(~EvanR@user/evanr) EvanR
2025-10-14 18:51:16 +0200Zemy(~Zemy@syn-076-184-041-021.res.spectrum.com)
2025-10-14 18:48:16 +0200EvanR(~EvanR@user/evanr) (Quit: Leaving)
2025-10-14 18:48:03 +0200machinedgod(~machinedg@d75-159-126-101.abhsia.telus.net) machinedgod
2025-10-14 18:43:47 +0200 <ski> in the `sortBy' example i gave above, there's no need for such nonsense, because the result is not a `Bool', but an `Ordering', and doing (short-circuiting) lexigographic composition of these seem to be the obvious choice of what `<>' should do, there
2025-10-14 18:43:41 +0200peterbecich(~Thunderbi@syn-172-222-148-214.res.spectrum.com) peterbecich
2025-10-14 18:43:33 +0200 <EvanR> so it all boils down to ways of stitching a bunch of things together with &&
2025-10-14 18:42:17 +0200 <ski> groupBy ((getAll .) . ((All .) . isIssuerOverlapping <> (All .) . isAssetOverlapping <> (All .) . isConditionOverlapping <> (All .) . isDateRangeOverlapping <> (All .) . isTargetColumnOverlapping)) -- the `(blah .) .' is annoying !
2025-10-14 18:41:53 +0200 <EvanR> monads requires a different shaped type, one with a parameter
2025-10-14 18:41:50 +0200 <Tri> sure, I will think about it
2025-10-14 18:41:23 +0200 <EvanR> i.e. folding Bools using &&
2025-10-14 18:41:13 +0200 <EvanR> short circuiting to False if there is a False is what `and' does
2025-10-14 18:41:00 +0200Zemy(~Zemy@syn-067-078-059-246.biz.spectrum.com) (Ping timeout: 244 seconds)
2025-10-14 18:40:59 +0200 <EvanR> I'm not sure that monads are appropriate for this
2025-10-14 18:40:43 +0200 <Tri> yes EvanR, in other words, short circuting to False, if there is a False. That resembles how bind works. I believe people have suggested to use <> and list comprehension, but I didn't have the mental capacity to read them yet, I'm working my day job at the moment