2024/10/22

Newest at the top

2024-10-22 14:28:44 +0200cfricke(~cfricke@user/cfricke) (Quit: WeeChat 4.2.2)
2024-10-22 14:28:38 +0200 <kqr> Leary, Ah, that could work. Do you have an example of that anywhere?
2024-10-22 14:28:13 +0200 <merijn> Hecate: Not directly, but Leary's approach works in recent enough cabals
2024-10-22 14:21:17 +0200identity(~identity@user/ZharMeny) identity
2024-10-22 14:20:59 +0200 <Leary> kqr: Put them in a private sub-library.
2024-10-22 14:19:29 +0200 <Hecate> Alas I don't think there's such a granularity of exposure available
2024-10-22 14:19:12 +0200 <Hecate> hmm
2024-10-22 14:16:21 +0200 <kqr> Is there a way to specify in a cabal file that certain modules in a library should not be exposed publically, but available to a test-suite?
2024-10-22 14:15:13 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Ping timeout: 248 seconds)
2024-10-22 14:10:49 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net)
2024-10-22 14:06:32 +0200mari-estel(~mari-este@user/mari-estel) mari-estel
2024-10-22 14:02:49 +0200tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2024-10-22 13:56:34 +0200madjestic(~madjestic@213.208.215.120) (Ping timeout: 265 seconds)
2024-10-22 13:53:41 +0200araujo(~araujo@45.146.55.99) (Ping timeout: 265 seconds)
2024-10-22 13:52:42 +0200TheCoffeMaker(~TheCoffeM@user/thecoffemaker) (Ping timeout: 265 seconds)
2024-10-22 13:50:10 +0200merijn(~merijn@77.242.116.146) merijn
2024-10-22 13:50:01 +0200eL_Bart0-(eL_Bart0@dietunichtguten.org)
2024-10-22 13:49:53 +0200eL_Bart0(eL_Bart0@dietunichtguten.org) (Quit: Restarting)
2024-10-22 13:48:57 +0200tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2024-10-22 13:48:08 +0200kuribas(~user@ip-188-118-57-242.reverse.destiny.be)
2024-10-22 13:46:38 +0200merijn(~merijn@77.242.116.146) (Ping timeout: 255 seconds)
2024-10-22 13:42:25 +0200TheCoffeMaker(~TheCoffeM@user/thecoffemaker) TheCoffeMaker
2024-10-22 13:38:46 +0200tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2024-10-22 13:33:46 +0200Clint(~Clint@user/clint) Clint
2024-10-22 13:31:36 +0200merijn(~merijn@77.242.116.146) merijn
2024-10-22 13:28:34 +0200CiaoSen(~Jura@2a05:5800:20b:3a00:ca4b:d6ff:fec1:99da) CiaoSen
2024-10-22 13:23:28 +0200merijn(~merijn@77.242.116.146) (Ping timeout: 252 seconds)
2024-10-22 13:19:41 +0200ljdarj(~Thunderbi@user/ljdarj) ljdarj
2024-10-22 13:16:56 +0200L29Ah(~L29Ah@wikipedia/L29Ah) L29Ah
2024-10-22 13:14:25 +0200araujo(~araujo@45.146.55.99)
2024-10-22 13:13:50 +0200xff0x(~xff0x@2405:6580:b080:900:61f:49ca:1cad:ed6)
2024-10-22 13:13:28 +0200merijn(~merijn@77.242.116.146) merijn
2024-10-22 13:11:29 +0200 <kaol> Still going to be a run time program breaking event if it happens.
2024-10-22 13:10:57 +0200 <tromp> yep; that "fixes" it
2024-10-22 13:10:32 +0200 <kaol> I always forget about lazy patterns.
2024-10-22 13:09:40 +0200madjestic(~madjestic@213.208.215.120) madjestic
2024-10-22 13:08:53 +0200 <mauke> ~(A b) <- ts
2024-10-22 13:07:36 +0200 <kaol> To expand on this a bit more: Having fail in Monad was always ugly since it's not a part of the definition in category theory and for many monads, you can't really do anything but invoke "error" if a pattern match failure happens and that's a silent source of partial functions.
2024-10-22 13:07:28 +0200merijn(~merijn@77.242.116.146) (Ping timeout: 245 seconds)
2024-10-22 13:04:46 +0200 <tromp> Thanks for help
2024-10-22 13:04:38 +0200 <kaol> If your purpose is to just follow some code at home, you may define your own MonadFail instance. But watch out if you think of doing the same in production.
2024-10-22 13:04:29 +0200ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 260 seconds)
2024-10-22 13:03:28 +0200 <kaol> They may be using an old GHC version or they may give it a catch all MonadFail instance. But this is the reason it won't work if you try it at home.
2024-10-22 13:02:28 +0200caconym(~caconym@user/caconym) caconym
2024-10-22 13:02:24 +0200 <tromp> oh, i can still run it online with the "Try it online! link
2024-10-22 13:01:41 +0200 <kaol> That's "old" for the purpose of this difference.
2024-10-22 13:01:09 +0200 <tromp> it's a post from 2017
2024-10-22 13:00:42 +0200 <kaol> Monad used to have "fail" as a part of it and old code on the Internet may still expect that to work.
2024-10-22 13:00:14 +0200 <tromp> and the author provides the output of running the code
2024-10-22 13:00:05 +0200alexherbo2(~alexherbo@2a02-8440-3211-c257-559a-6e1d-739b-a378.rev.sfr.net) alexherbo2