2023/03/03

2023-03-03 00:01:19 +0100thaumavorio_(~thaumavor@thaumavor.io) (Quit: ZNC 1.8.2 - https://znc.in)
2023-03-03 00:02:40 +0100Guest58(~textual@2603-7000-1203-4d7c-0cdc-f6ea-1da9-3494.res6.spectrum.com) (Quit: ZZZzzz…)
2023-03-03 00:03:13 +0100thaumavorio(~thaumavor@thaumavor.io)
2023-03-03 00:07:26 +0100Sauvin(~sauvin@user/Sauvin) (Quit: Leaving)
2023-03-03 00:09:06 +0100bilegeek(~bilegeek@2600:1008:b011:7459:a819:7768:fb22:1ebd)
2023-03-03 00:09:08 +0100Sauvin(~sauvin@user/Sauvin)
2023-03-03 00:09:32 +0100gmg(~user@user/gehmehgeh) (Quit: Leaving)
2023-03-03 00:10:20 +0100fnurglewitz(uid263868@id-263868.lymington.irccloud.com) (Quit: Connection closed for inactivity)
2023-03-03 00:21:25 +0100jpds(~jpds@gateway/tor-sasl/jpds) (Remote host closed the connection)
2023-03-03 00:25:20 +0100werneta(~werneta@137.79.212.16) (Remote host closed the connection)
2023-03-03 00:26:47 +0100jpds(~jpds@gateway/tor-sasl/jpds)
2023-03-03 00:32:39 +0100acidjnk_new(~acidjnk@p200300d6e715c424d939d96a9ad2afa1.dip0.t-ipconnect.de) (Ping timeout: 260 seconds)
2023-03-03 00:34:05 +0100dekster(~dekster@2603-7000-1203-4d7c-0cdc-f6ea-1da9-3494.res6.spectrum.com)
2023-03-03 00:38:31 +0100bontaq(~user@ool-45779fe5.dyn.optonline.net)
2023-03-03 00:39:41 +0100azimut_(~azimut@gateway/tor-sasl/azimut) (Remote host closed the connection)
2023-03-03 00:39:46 +0100califax(~califax@user/califx) (Remote host closed the connection)
2023-03-03 00:40:31 +0100azimut(~azimut@gateway/tor-sasl/azimut)
2023-03-03 00:40:45 +0100Square3(~Square4@user/square)
2023-03-03 00:40:56 +0100califax(~califax@user/califx)
2023-03-03 00:47:54 +0100catern(~sbaugh@2604:2000:8fc0:b:a9c7:866a:bf36:3407) (Read error: Connection reset by peer)
2023-03-03 00:53:17 +0100califax(~califax@user/califx) (Ping timeout: 255 seconds)
2023-03-03 00:53:27 +0100califax_(~califax@user/califx)
2023-03-03 00:53:44 +0100jpds(~jpds@gateway/tor-sasl/jpds) (Ping timeout: 255 seconds)
2023-03-03 00:54:42 +0100califax_califax
2023-03-03 00:55:06 +0100manwithluck(manwithluc@hoeven.dossingday.ml) (Quit: ZNC - https://znc.in)
2023-03-03 00:56:05 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2023-03-03 00:56:47 +0100jpds(~jpds@gateway/tor-sasl/jpds)
2023-03-03 01:01:07 +0100anatta_(~AdiIRC@h-155-4-132-216.na.cust.bahnhof.se)
2023-03-03 01:03:26 +0100califax(~califax@user/califx) (Remote host closed the connection)
2023-03-03 01:03:56 +0100califax(~califax@user/califx)
2023-03-03 01:04:16 +0100anatta(~AdiIRC@h-155-4-132-216.NA.cust.bahnhof.se) (Ping timeout: 265 seconds)
2023-03-03 01:04:26 +0100anatta_anatta
2023-03-03 01:05:41 +0100mauke_(~mauke@user/mauke)
2023-03-03 01:05:55 +0100zeenk(~zeenk@2a02:2f04:a20d:f900::7fe) (Quit: Konversation terminated!)
2023-03-03 01:07:07 +0100isovector(~isovector@172.103.235.56.cable.tpia.cipherkey.com)
2023-03-03 01:07:13 +0100 <isovector> does anyone have experience with ghc-debug?
2023-03-03 01:07:17 +0100Inst(~Inst@2601:6c4:4081:54f0:e1bb:9a51:4c8c:9c0a)
2023-03-03 01:07:27 +0100 <Inst> hmmm, a bit laggy
2023-03-03 01:07:31 +0100mauke(~mauke@user/mauke) (Ping timeout: 268 seconds)
2023-03-03 01:07:32 +0100mauke_mauke
2023-03-03 01:07:51 +0100 <Inst> question, if I want to run a Haskell compiled program, but hide the console, what would I do?
2023-03-03 01:08:00 +0100dekster(~dekster@2603-7000-1203-4d7c-0cdc-f6ea-1da9-3494.res6.spectrum.com) (Quit: ZZZzzz…)
2023-03-03 01:09:37 +0100 <hpc> you're on windows, i take it?
2023-03-03 01:12:15 +0100Monster196883(~hp@103.15.228.66) (Ping timeout: 248 seconds)
2023-03-03 01:14:18 +0100dekster(~dekster@2603-7000-1203-4d7c-0cdc-f6ea-1da9-3494.res6.spectrum.com)
2023-03-03 01:14:19 +0100 <Inst> yeah
2023-03-03 01:14:29 +0100 <Inst> also, a question about combinator first vs outline first approach
2023-03-03 01:14:36 +0100 <Inst> are those the two main approaches to hacking in Haskell?
2023-03-03 01:15:04 +0100 <Inst> my experience is that an outline first / control first approach tends to create really IO heavy programs, whereas a combinator first approach gets you purity at the outset
2023-03-03 01:15:45 +0100 <Inst> so far, my understanding of Haskell is, if you're horrified at how much IO code you're making and how ugly it is, go to a framework which handles the IO for you
2023-03-03 01:16:12 +0100 <Inst> i.e, a servant server is essentially IO heavy, but the IO code is hidden by the Servant framework
2023-03-03 01:17:08 +0100Pickchea(~private@user/pickchea) (Quit: Leaving)
2023-03-03 01:21:58 +0100isovector(~isovector@172.103.235.56.cable.tpia.cipherkey.com) ()
2023-03-03 01:22:03 +0100caryhartline(~caryhartl@2600:1700:2d0:8d30:2d25:9310:79f2:85fd)
2023-03-03 01:22:06 +0100tubogram44(~tubogram@user/tubogram) (Quit: See ya later!)
2023-03-03 01:24:48 +0100dekster(~dekster@2603-7000-1203-4d7c-0cdc-f6ea-1da9-3494.res6.spectrum.com) (Quit: ZZZzzz…)
2023-03-03 01:24:51 +0100 <Inst> so i guess this is a question about a standard EDSL for Haskell IO work
2023-03-03 01:26:05 +0100 <hpc> IO isn't necessarily a bad thing, just having it appear where it's inappropriate is
2023-03-03 01:26:20 +0100 <hpc> it's like Maybe, which is literally just a different name for the billion dollar mistake
2023-03-03 01:26:59 +0100 <hpc> being able to pass around IO actions as plain values is quite powerful
2023-03-03 01:28:15 +0100 <hpc> as for how to design software, it depends
2023-03-03 01:28:22 +0100 <hpc> i kind of just start at the part i understand the most
2023-03-03 01:28:48 +0100 <hpc> sometimes that's an outline, sometimes it's a couple of useful functions, and sometimes it's not even the code itself but how i fit it into something else
2023-03-03 01:29:25 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-03-03 01:30:25 +0100jwiegley(~jwiegley@2600:1700:cf00:db0:240d:4ecd:e535:2c8f) (Quit: ZNC - http://znc.in)
2023-03-03 01:30:25 +0100johnw(~johnw@2600:1700:cf00:db0:240d:4ecd:e535:2c8f) (Quit: ZNC - http://znc.in)
2023-03-03 01:31:11 +0100emmanuelux(~emmanuelu@user/emmanuelux) (Quit: au revoir)
2023-03-03 01:31:11 +0100tubogram44(~tubogram@user/tubogram)
2023-03-03 01:31:48 +0100 <Inst> yeah, I was really into "pseudo-code driven design" a while back, i.e, build a skeleton of your program then implement
2023-03-03 01:32:06 +0100 <Inst> now I'm realizing that starting from combinators has its own value, and your advice about starting from base is probably a good idea as well
2023-03-03 01:32:27 +0100 <Inst> I'm also thinking about EDSLs in Haskell, like, this is literally the Haskell equivalent of Lisp "need a capability and it's not provided for you? Build an EDSL."
2023-03-03 01:32:55 +0100 <Inst> it's hard to get Haskell code to be cleaner and nicer than Python code when you're working imperatively, so, solution might be to build an EDSL + interpreter
2023-03-03 01:33:08 +0100 <Inst> not sure if someone's identified this as a problem and tried it yet
2023-03-03 01:33:15 +0100 <hpc> i find it's the opposite, and i can get haskell way cleaner
2023-03-03 01:33:57 +0100 <Inst> skill deficit here, I guess
2023-03-03 01:34:03 +0100 <hpc> for example, i have written code in both languages that is more or less a job queue feeding into multiple runners
2023-03-03 01:34:08 +0100 <Inst> sm offered to help me code-golf, might be able to find people interested in translating Hasklel to Python
2023-03-03 01:34:23 +0100 <Inst> I'm that accursed freak, someone who picked up Haskell as a first language and found it simpler than imperative langs
2023-03-03 01:34:33 +0100 <Inst> wish we could make it that way for tons more people instead
2023-03-03 01:34:36 +0100 <hpc> a basic thread pool and queue that they all pull from takes me maybe 10 lines of haskell without even needing to install packages
2023-03-03 01:35:11 +0100 <hpc> in python it's 50-ish lines of wrapping around some other object that already does almost everything
2023-03-03 01:37:09 +0100 <hpc> i probably could have gotten the python cleaner if i tried harder, but i was sick of fixing all the bugs and i only had to spend an hour on the haskell code
2023-03-03 01:37:28 +0100 <hpc> forkIO and Chan are just too good at what they do :D
2023-03-03 01:39:45 +0100caryhartline(~caryhartl@2600:1700:2d0:8d30:2d25:9310:79f2:85fd) (Ping timeout: 260 seconds)
2023-03-03 01:39:52 +0100Tuplanolla(~Tuplanoll@91-159-68-152.elisa-laajakaista.fi) (Quit: Leaving.)
2023-03-03 01:41:20 +0100sammelweis(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Quit: No Ping reply in 180 seconds.)
2023-03-03 01:45:10 +0100 <monochrom> "translate" is always wrong.
2023-03-03 01:45:42 +0100sammelweis(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10)
2023-03-03 01:46:35 +0100 <monochrom> You can use a fork to eat noodles, and you will develop a technique that plays to the strength of a fork.
2023-03-03 01:47:02 +0100 <monochrom> You can use a pair of chopsticks to eat noodles, and you will develop a technique that plays to the strength of chopsticks.
2023-03-03 01:47:17 +0100 <monochrom> No one talks about translating fork to chopsticks or vice versa.
2023-03-03 01:47:28 +0100 <jackdk> monochrom: Just reverse the forks and use the non-tined ends like chopsticks. Simple.
2023-03-03 01:47:44 +0100 <monochrom> haha but then you'll need two forks.
2023-03-03 01:48:04 +0100 <monochrom> Ah is that how DIjkstra thought up the dining philosopher problem >:)
2023-03-03 01:48:22 +0100jero98772(~jero98772@2800:484:1d80:d8ce:efcc:cbb3:7f2a:6dff)
2023-03-03 01:50:06 +0100 <jackdk> The dining philosophers make so much more sense if you have chopsticks, yes.
2023-03-03 01:51:04 +0100 <monochrom> I was marking an assignment that asked students to solve a problem in Prolog, Haskell, and Python. I had a student whose Python code did not play to the strength of Python OO, instead abuse isinstanceof to emulate Haskell pattern matching. I gave a low mark. It's a dumb approach.
2023-03-03 01:51:42 +0100 <jackdk> doesn't python have native pattern matching of sorts now?
2023-03-03 01:52:00 +0100 <monochrom> I don't know. The student didn't use that anyway.
2023-03-03 01:57:05 +0100 <monochrom> "how to teach chopsticks to more people" is a good question. "how to teach chopsticks to more people by translating to/from fork" is a stupid question.
2023-03-03 01:57:29 +0100sammelweis_(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10)
2023-03-03 01:57:36 +0100sammelweis(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Ping timeout: 248 seconds)
2023-03-03 01:59:46 +0100 <monochrom> And BTW today's HWN features https://dev.to/zelenya/there-is-no-tooling-issue-in-haskell-cal 'There is No “Tooling Issue” in Haskell' so stop worrying about a solved problem.
2023-03-03 02:07:19 +0100bitmapper(uid464869@id-464869.lymington.irccloud.com)
2023-03-03 02:09:31 +0100wroathe(~wroathe@207-153-38-140.fttp.usinternet.com)
2023-03-03 02:09:31 +0100wroathe(~wroathe@207-153-38-140.fttp.usinternet.com) (Changing host)
2023-03-03 02:09:31 +0100wroathe(~wroathe@user/wroathe)
2023-03-03 02:10:07 +0100azimut_(~azimut@gateway/tor-sasl/azimut)
2023-03-03 02:10:41 +0100azimut(~azimut@gateway/tor-sasl/azimut) (Ping timeout: 255 seconds)
2023-03-03 02:10:51 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Remote host closed the connection)
2023-03-03 02:11:32 +0100 <c_wraith> I mean.. the tooling is a lot better than some people claim. But there are definitely things to improve. (And I see lots of effort into improving them!)
2023-03-03 02:12:33 +0100 <monochrom> Yeah perhaps s/worrying/doomsaying/
2023-03-03 02:16:58 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-03-03 02:19:08 +0100machinedgod(~machinedg@d198-53-218-113.abhsia.telus.net) (Remote host closed the connection)
2023-03-03 02:23:11 +0100mncheck(~mncheck@193.224.205.254) (Ping timeout: 246 seconds)
2023-03-03 02:23:44 +0100sammelweis_(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Quit: No Ping reply in 180 seconds.)
2023-03-03 02:24:11 +0100FinnElija(~finn_elij@user/finn-elija/x-0085643) (Ping timeout: 255 seconds)
2023-03-03 02:25:02 +0100sammelweis(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10)
2023-03-03 02:25:43 +0100machinedgod(~machinedg@d198-53-218-113.abhsia.telus.net)
2023-03-03 02:26:19 +0100FinnElija(~finn_elij@user/finn-elija/x-0085643)
2023-03-03 02:32:06 +0100cheater(~Username@user/cheater) (Remote host closed the connection)
2023-03-03 02:35:28 +0100eggplantade(~Eggplanta@2600:1700:38c5:d800:8429:4ceb:8103:61ef)
2023-03-03 02:38:13 +0100lbseale(~quassel@user/ep1ctetus) (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)
2023-03-03 02:38:45 +0100lbseale(~quassel@user/ep1ctetus)
2023-03-03 02:39:02 +0100dtman34(~dtman34@2601:447:d000:93c9:2198:73de:f8ee:642a) (Quit: ZNC 1.8.2+deb2+b1 - https://znc.in)
2023-03-03 02:39:23 +0100dtman34(~dtman34@76.156.89.180)
2023-03-03 02:39:37 +0100 <sm> the title is a little strong, but that's a nice article
2023-03-03 02:39:43 +0100eggplantade(~Eggplanta@2600:1700:38c5:d800:8429:4ceb:8103:61ef) (Ping timeout: 248 seconds)
2023-03-03 02:40:35 +0100 <bramhaag> How would one force megaparsec to commit to an alternative if a certain condition holds? i.e 'commit (pure True) p <|> commit (pure False) q' would fail if p fails
2023-03-03 02:46:15 +0100xff0x(~xff0x@ai081074.d.east.v6connect.net) (Ping timeout: 260 seconds)
2023-03-03 02:58:51 +0100cheater(~Username@user/cheater)
2023-03-03 03:01:42 +0100dekster(~dekster@2603-7000-1203-4d7c-143a-d742-ee9b-9bc6.res6.spectrum.com)
2023-03-03 03:02:04 +0100abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net) (Ping timeout: 246 seconds)
2023-03-03 03:07:27 +0100bontaq(~user@ool-45779fe5.dyn.optonline.net) (Ping timeout: 248 seconds)
2023-03-03 03:08:09 +0100abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net)
2023-03-03 03:08:41 +0100dekster(~dekster@2603-7000-1203-4d7c-143a-d742-ee9b-9bc6.res6.spectrum.com) (Quit: bb)
2023-03-03 03:09:40 +0100dekster(~dekster@2603-7000-1203-4d7c-143a-d742-ee9b-9bc6.res6.spectrum.com)
2023-03-03 03:14:40 +0100dekster(~dekster@2603-7000-1203-4d7c-143a-d742-ee9b-9bc6.res6.spectrum.com) (Quit: bb)
2023-03-03 03:15:28 +0100mmhat(~mmh@p200300f1c70462d7ee086bfffe095315.dip0.t-ipconnect.de) (Quit: WeeChat 3.8)
2023-03-03 03:19:44 +0100travisb_tabemann
2023-03-03 03:21:07 +0100Lord_of_Life_(~Lord@user/lord-of-life/x-2819915)
2023-03-03 03:21:21 +0100Lord_of_Life(~Lord@user/lord-of-life/x-2819915) (Ping timeout: 255 seconds)
2023-03-03 03:22:24 +0100Lord_of_Life_Lord_of_Life
2023-03-03 03:24:41 +0100segfaultfizzbuzz(~segfaultf@23-93-74-212.fiber.dynamic.sonic.net)
2023-03-03 03:24:48 +0100 <segfaultfizzbuzz> https://www.basis.ai/blog/autumn/ this was pretty awesome
2023-03-03 03:25:57 +0100 <segfaultfizzbuzz> even if this turns out to not really work, even the idea of trying to guess a program via observation is awesome
2023-03-03 03:29:33 +0100 <zero> i'm trying to choose a good library to create simple soundwaves (think a *very* basic synth) over a gloss interactive animation. would something like OpenAL be a good choice or overkill?
2023-03-03 03:36:26 +0100xff0x(~xff0x@125x103x176x34.ap125.ftth.ucom.ne.jp)
2023-03-03 03:37:22 +0100mechap(~mechap@user/mechap) (Ping timeout: 268 seconds)
2023-03-03 03:38:32 +0100Square3Square
2023-03-03 03:38:48 +0100L29Ah(~L29Ah@wikipedia/L29Ah) (Ping timeout: 255 seconds)
2023-03-03 03:39:16 +0100mechap(~mechap@user/mechap)
2023-03-03 03:42:03 +0100 <segfaultfizzbuzz> zero: i haven't used them myself but i think nobody got fired for using libSDL bindings...
2023-03-03 03:43:49 +0100thegeekinside(~thegeekin@189.141.115.134) (Remote host closed the connection)
2023-03-03 03:43:54 +0100merijn(~merijn@86-86-29-250.fixed.kpn.net)
2023-03-03 03:47:00 +0100wroathe(~wroathe@user/wroathe) (Ping timeout: 255 seconds)
2023-03-03 03:48:21 +0100merijn(~merijn@86-86-29-250.fixed.kpn.net) (Ping timeout: 255 seconds)
2023-03-03 03:50:33 +0100king_gs(~Thunderbi@187.201.41.239)
2023-03-03 03:50:39 +0100 <zero> ok this seems fine. tx
2023-03-03 03:50:39 +0100 <sm> zero: if you don't mind running an external program, `sox synth` can be very quick
2023-03-03 03:51:34 +0100razetime(~Thunderbi@117.193.1.135)
2023-03-03 03:53:06 +0100gurkenglas(~gurkengla@dynamic-046-114-178-010.46.114.pool.telefonica.de)
2023-03-03 04:12:13 +0100mrcsnotitus
2023-03-03 04:12:20 +0100titustitusgroen
2023-03-03 04:12:43 +0100titusgroenmrcsno
2023-03-03 04:15:07 +0100jero98772(~jero98772@2800:484:1d80:d8ce:efcc:cbb3:7f2a:6dff) (Remote host closed the connection)
2023-03-03 04:18:54 +0100sammelweis(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Quit: No Ping reply in 180 seconds.)
2023-03-03 04:19:27 +0100machinedgod(~machinedg@d198-53-218-113.abhsia.telus.net) (Ping timeout: 248 seconds)
2023-03-03 04:20:11 +0100sammelweis(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10)
2023-03-03 04:21:52 +0100johnw(~johnw@76-234-69-149.lightspeed.frokca.sbcglobal.net)
2023-03-03 04:22:22 +0100jwiegley(~jwiegley@2600:1700:cf00:db0:941:22ec:3d83:e77a)
2023-03-03 04:23:58 +0100gastus(~gastus@185.6.123.181)
2023-03-03 04:25:28 +0100king_gs(~Thunderbi@187.201.41.239) (Ping timeout: 268 seconds)
2023-03-03 04:26:55 +0100gastus_(~gastus@5.83.191.44) (Ping timeout: 248 seconds)
2023-03-03 04:34:32 +0100finn_elija(~finn_elij@user/finn-elija/x-0085643)
2023-03-03 04:34:32 +0100FinnElija(~finn_elij@user/finn-elija/x-0085643) (Killed (NickServ (Forcing logout FinnElija -> finn_elija)))
2023-03-03 04:34:32 +0100finn_elijaFinnElija
2023-03-03 04:36:30 +0100td_(~td@i5387090D.versanet.de) (Ping timeout: 255 seconds)
2023-03-03 04:37:09 +0100eggplantade(~Eggplanta@2600:1700:38c5:d800:8429:4ceb:8103:61ef)
2023-03-03 04:37:56 +0100king_gs(~Thunderbi@187.201.41.239)
2023-03-03 04:38:11 +0100td_(~td@i5387090C.versanet.de)
2023-03-03 04:39:43 +0100segfaultfizzbuzz(~segfaultf@23-93-74-212.fiber.dynamic.sonic.net) (Ping timeout: 248 seconds)
2023-03-03 04:41:34 +0100eggplantade(~Eggplanta@2600:1700:38c5:d800:8429:4ceb:8103:61ef) (Ping timeout: 252 seconds)
2023-03-03 04:42:48 +0100segfaultfizzbuzz(~segfaultf@23-93-74-212.fiber.dynamic.sonic.net)
2023-03-03 04:44:56 +0100bilegeek(~bilegeek@2600:1008:b011:7459:a819:7768:fb22:1ebd) (Remote host closed the connection)
2023-03-03 04:45:21 +0100bilegeek(~bilegeek@2600:1008:b011:7459:a819:7768:fb22:1ebd)
2023-03-03 04:48:15 +0100vglfr(~vglfr@145.224.100.119) (Ping timeout: 248 seconds)
2023-03-03 04:49:13 +0100vglfr(~vglfr@145.224.100.119)
2023-03-03 04:55:16 +0100 <Inst> There is still a tooling issue in Haskell, monochrom. Every time I press ctrl shift p in VSC, I learn how tooling isn't good.
2023-03-03 04:55:39 +0100 <Inst> But it's much improved from the Cabal hell days, where you had to struggle to make Haskell usable. Haskell is perfectly usable, just not good or excellent at this stage.
2023-03-03 04:55:51 +0100 <zero> what's ctrl+shift+p in vsc?
2023-03-03 04:56:09 +0100 <Inst> bring up options, then restart HLS
2023-03-03 04:56:18 +0100 <segfaultfizzbuzz> zerp: that prints to the printer in all caps
2023-03-03 04:56:27 +0100 <Inst> updated my cabal file
2023-03-03 04:56:31 +0100 <zero> segfaultfizzbuzz: lol
2023-03-03 04:56:38 +0100 <segfaultfizzbuzz> zero: it's called "paper shout"
2023-03-03 04:57:39 +0100king_gs(~Thunderbi@187.201.41.239) (Read error: Connection reset by peer)
2023-03-03 04:59:42 +0100 <zero> is that a problem with haskell tooling or LSPs in general?
2023-03-03 04:59:57 +0100bilegeek(~bilegeek@2600:1008:b011:7459:a819:7768:fb22:1ebd) (Remote host closed the connection)
2023-03-03 05:00:08 +0100 <Inst> possibly, well, it's not rereading my cabal file, or HLS / GHCIde crashed
2023-03-03 05:00:25 +0100bilegeek(~bilegeek@2600:1008:b011:7459:a819:7768:fb22:1ebd)
2023-03-03 05:00:51 +0100 <Inst> i'm not really criticizing Haskell, tbh, I still love it, albeit I still can't figure out how to get better scripting code than Python, which is sort of an outrageous request given that Python is designed as a scripting language
2023-03-03 05:01:13 +0100 <Inst> everything that's wrong gets fixed in time, like how Haskell Error Index is now a thing
2023-03-03 05:01:41 +0100 <Inst> and how we went from Cabal Hell, to Stack, back to a new and improved Cabal
2023-03-03 05:05:39 +0100waleee(~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7) (Ping timeout: 260 seconds)
2023-03-03 05:06:09 +0100eggplantade(~Eggplanta@104-55-37-220.lightspeed.sntcca.sbcglobal.net)
2023-03-03 05:07:22 +0100bilegeek_(~bilegeek@2600:1008:b022:5533:8b20:d196:1708:e74e)
2023-03-03 05:08:05 +0100zerozzz
2023-03-03 05:10:20 +0100bilegeek(~bilegeek@2600:1008:b011:7459:a819:7768:fb22:1ebd) (Ping timeout: 260 seconds)
2023-03-03 05:10:42 +0100stiell(~stiell@gateway/tor-sasl/stiell) (Remote host closed the connection)
2023-03-03 05:11:13 +0100stiell(~stiell@gateway/tor-sasl/stiell)
2023-03-03 05:12:05 +0100bilegeek_(~bilegeek@2600:1008:b022:5533:8b20:d196:1708:e74e) (Ping timeout: 260 seconds)
2023-03-03 05:13:35 +0100gurkenglas(~gurkengla@dynamic-046-114-178-010.46.114.pool.telefonica.de) (Ping timeout: 268 seconds)
2023-03-03 05:21:31 +0100use-value(~Thunderbi@2a00:23c6:8a03:2f01:75c2:a71f:beaa:29bf) (Remote host closed the connection)
2023-03-03 05:21:50 +0100use-value(~Thunderbi@2a00:23c6:8a03:2f01:75c2:a71f:beaa:29bf)
2023-03-03 05:22:59 +0100mbuf(~Shakthi@49.204.138.106)
2023-03-03 05:28:28 +0100remsense(~iarmatrix@2001:470:69fc:105::3:625)
2023-03-03 05:30:48 +0100kupi(uid212005@id-212005.hampstead.irccloud.com) (Quit: Connection closed for inactivity)
2023-03-03 05:36:14 +0100razetime(~Thunderbi@117.193.1.135) (Ping timeout: 255 seconds)
2023-03-03 05:36:15 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 05:36:31 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:36:31 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:36:48 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:36:48 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:37:04 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:37:04 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 05:37:20 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:37:20 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:37:36 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:37:36 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:37:52 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:37:53 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 05:38:09 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:38:09 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 05:38:24 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:38:24 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:38:36 +0100vglfr(~vglfr@145.224.100.119) (Ping timeout: 255 seconds)
2023-03-03 05:38:41 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:38:42 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:38:57 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:38:57 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:39:13 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:39:13 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:39:17 +0100jwiegley(~jwiegley@2600:1700:cf00:db0:941:22ec:3d83:e77a) (Quit: ZNC - http://znc.in)
2023-03-03 05:39:17 +0100johnw(~johnw@76-234-69-149.lightspeed.frokca.sbcglobal.net) (Quit: ZNC - http://znc.in)
2023-03-03 05:39:30 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:39:30 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:39:47 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:39:47 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:40:02 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:40:03 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 05:40:19 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:40:20 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:40:34 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:40:35 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 05:40:51 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:40:52 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 05:41:08 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:41:09 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 05:41:24 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:41:24 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:41:40 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:41:41 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 05:41:44 +0100adanwan(~adanwan@gateway/tor-sasl/adanwan) (Ping timeout: 255 seconds)
2023-03-03 05:41:56 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:41:56 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:42:12 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:42:12 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:42:28 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:42:28 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:42:44 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:42:44 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:43:01 +0100adanwan(~adanwan@gateway/tor-sasl/adanwan)
2023-03-03 05:43:01 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:43:02 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 05:43:18 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:43:18 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:43:35 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:43:36 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 05:43:52 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:43:52 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:44:05 +0100Inst(~Inst@2601:6c4:4081:54f0:e1bb:9a51:4c8c:9c0a) (Read error: Connection reset by peer)
2023-03-03 05:44:08 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:44:08 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:44:24 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:44:25 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 05:44:31 +0100Inst(~Inst@2601:6c4:4081:54f0:e1bb:9a51:4c8c:9c0a)
2023-03-03 05:44:40 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:44:41 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:44:55 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:44:55 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:45:11 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:45:12 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 05:45:26 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:45:26 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:45:41 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:45:42 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:45:57 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:45:58 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 05:46:13 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:46:14 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:46:29 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:46:29 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:46:45 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:46:46 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 05:47:02 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:47:03 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:47:18 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:47:18 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:47:33 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:47:33 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:47:48 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:47:49 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 05:48:04 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:48:04 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:48:20 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:48:20 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:48:36 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:48:36 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 05:48:53 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:48:53 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 05:49:08 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:49:08 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:49:23 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:49:24 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 05:49:40 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:49:40 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:49:56 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:49:56 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:50:11 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:50:11 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:50:27 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:50:27 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:50:44 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:50:45 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:50:59 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:51:00 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 05:51:15 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:51:15 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:51:31 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:51:31 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:51:47 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:51:47 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:52:03 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:52:03 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:52:18 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:52:19 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 05:52:35 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:52:36 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:52:51 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:52:51 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:53:00 +0100wroathe(~wroathe@207-153-38-140.fttp.usinternet.com)
2023-03-03 05:53:00 +0100wroathe(~wroathe@207-153-38-140.fttp.usinternet.com) (Changing host)
2023-03-03 05:53:00 +0100wroathe(~wroathe@user/wroathe)
2023-03-03 05:53:07 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:53:08 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:53:24 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:53:24 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:53:41 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:53:41 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:53:56 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:53:56 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:54:10 +0100polyphem_(~rod@2a02:810d:840:8754:224e:f6ff:fe5e:bc17) (Ping timeout: 252 seconds)
2023-03-03 05:54:11 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:54:11 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:54:27 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:54:27 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:54:44 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:54:44 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:55:00 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:55:00 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:55:16 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:55:16 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:55:31 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:55:31 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:55:47 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:55:47 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:56:04 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:56:04 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:56:19 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:56:19 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:56:35 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:56:35 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:56:50 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:56:50 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:57:05 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:57:05 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:57:22 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:57:22 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:57:37 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:57:37 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:57:53 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:57:53 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:58:09 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:58:09 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:58:25 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:58:25 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:58:41 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:58:41 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:58:57 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:58:57 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:59:09 +0100dsrt^(~dsrt@c-24-30-76-89.hsd1.ga.comcast.net)
2023-03-03 05:59:12 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:59:12 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:59:28 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:59:28 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:59:43 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:59:43 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 05:59:59 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 05:59:59 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:00:14 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:00:14 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:00:30 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:00:30 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:00:46 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:00:46 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:01:01 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:01:01 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:01:16 +0100vglfr(~vglfr@145.224.100.65)
2023-03-03 06:01:17 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:01:17 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:01:33 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:01:33 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:01:48 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:01:48 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:02:03 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:02:03 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:02:18 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:02:18 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:02:33 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:02:33 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:02:49 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:02:49 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:03:05 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:03:05 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:03:21 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:03:21 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:03:37 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:03:37 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:03:52 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:03:52 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:04:08 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:04:09 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:04:25 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:04:25 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:04:42 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:04:42 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:04:58 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:04:58 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:05:14 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:05:14 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:05:30 +0100dcoutts_(~duncan@cpc69403-oxfd27-2-0-cust285.4-3.cable.virginm.net)
2023-03-03 06:05:30 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:05:30 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:05:47 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:05:47 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:06:03 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:06:03 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:06:19 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:06:20 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:06:35 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:06:35 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:06:52 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:06:52 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:07:07 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:07:07 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:07:11 +0100wroathe(~wroathe@user/wroathe) (Ping timeout: 248 seconds)
2023-03-03 06:07:23 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:07:23 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:07:38 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:07:38 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:07:54 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:07:54 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:08:10 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:08:10 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:08:25 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:08:25 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:08:42 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:08:42 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:08:58 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:08:58 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:09:14 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:09:14 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:09:31 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:09:31 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:09:46 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:09:46 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:10:03 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:10:03 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:10:15 +0100 <Clinton[m]> So I've started thinking that using `MonadIO m` in a lot of places is a bad idea, and I should probably use `MonadLogger m` or `MonadHTTP m` or `MonadBlah m` etc. Problem is then presumably I'll need a bunch of instances `MonadX m => MonadX (BlahTransT m)` for at least the common transformers, for every `MonadX`, which seems a bit boilerplatey. Is there a nicer way to achieve this?
2023-03-03 06:10:20 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:10:21 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:10:37 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:10:38 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:10:43 +0100silverwhitefish(~hidden@47.202.102.229)
2023-03-03 06:10:52 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:10:52 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:11:08 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:11:08 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:11:10 +0100silverwhitefish(~hidden@47.202.102.229) (Client Quit)
2023-03-03 06:11:24 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:11:25 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:11:40 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:11:41 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:11:57 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:11:57 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:12:13 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:12:13 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:12:29 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:12:30 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:12:45 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:12:45 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:13:01 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:13:01 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:13:16 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:13:16 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:13:31 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:13:32 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:13:46 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:13:46 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:14:02 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:14:02 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:14:18 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:14:18 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:14:34 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:14:35 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:14:39 +0100segfaultfizzbuzz(~segfaultf@23-93-74-212.fiber.dynamic.sonic.net) (Ping timeout: 248 seconds)
2023-03-03 06:14:49 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:14:50 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:15:05 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:15:05 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:15:19 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:15:19 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:15:36 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:15:36 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:15:51 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:15:51 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:16:06 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:16:06 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:16:22 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:16:22 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:16:37 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:16:38 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:16:52 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:16:52 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:17:06 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:17:06 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:17:22 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:17:23 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:17:39 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:17:40 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:17:56 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:17:56 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:18:11 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:18:11 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:18:26 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:18:27 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:18:43 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:18:44 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:19:00 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:19:01 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:19:16 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:19:17 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:19:33 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:19:34 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:19:49 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:19:49 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:20:05 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:20:06 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:20:22 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:20:22 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:20:39 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:20:39 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:20:55 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:20:56 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:21:10 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:21:10 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:21:25 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:21:25 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:21:39 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:21:39 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:21:55 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:21:56 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:22:11 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:22:11 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:22:28 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:22:28 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:22:42 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:22:42 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:22:58 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:22:58 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:23:14 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:23:15 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:23:29 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:23:29 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:23:43 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:23:43 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:23:57 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:23:57 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:24:13 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:24:13 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:24:28 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:24:28 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:24:44 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:24:44 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:25:00 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:25:00 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:25:16 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:25:16 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:25:33 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:25:33 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:25:49 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:25:49 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:25:57 +0100 <jackdk> Write a single concrete application monad and implement all the instances against that. Consider the "phantom datakinds" pattern for mocking during tests: https://chrispenner.ca/posts/mock-effects-with-data-kinds . Or move to an effect system
2023-03-03 06:26:05 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:26:05 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:26:21 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:26:21 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:26:37 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:26:37 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:26:51 +0100 <mauke> monochrom: https://i.imgur.com/tILWA1z.png
2023-03-03 06:26:54 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:26:54 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:27:04 +0100 <jackdk> But yeah, you've hit the famous "n^2 instances problem", which is precise (not every class can be lifted through every transformer) but annoyingly boilerplatey
2023-03-03 06:27:10 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:27:10 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:27:17 +0100 <jackdk> mauke: hahaha, great find
2023-03-03 06:27:26 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:27:26 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:27:42 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:27:42 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:27:58 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:27:58 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:28:13 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:28:13 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:28:29 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:28:29 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:28:45 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:28:45 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:28:52 +0100 <Clinton[m]> jackdk: After some thought, I think most of the things I need to do this with is with IO. So I think this will do the trick I think:... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/798a6d8c648acfe8a425a9715c72c2623719…>)
2023-03-03 06:29:01 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:29:01 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:29:17 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:29:18 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:29:34 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:29:34 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:29:50 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:29:51 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:30:06 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:30:06 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:30:22 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:30:22 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:30:39 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:30:39 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:30:54 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:30:54 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:31:10 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:31:10 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:31:19 +0100 <jackdk> Clinton[m]: bear in mind that will match _every_ monad, because instance selection only looks at the _shape_ of the type constructors, and only adds constraints after it selects an instance
2023-03-03 06:31:25 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:31:25 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:31:41 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:31:41 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:31:57 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:31:57 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:32:13 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:32:13 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:32:15 +0100 <Clinton[m]> jackdk: yeah the idea is that there's only one instance anyway.
2023-03-03 06:32:29 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:32:29 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:32:41 +0100 <jackdk> Then I don't see what you gain by adding these classes (except sore fingers)
2023-03-03 06:32:45 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:32:45 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:33:00 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:33:01 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:33:15 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:33:15 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:33:30 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:33:30 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:33:46 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:33:46 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:33:47 +0100 <jackdk> https://journal.infinitenegativeutility.com/haskell-type-equality-constraints Clinton[m] you may already know this, but this is what I'm talking about re: instance selection
2023-03-03 06:34:03 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:34:03 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:34:05 +0100 <Clinton[m]> jackdk:... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/9fd0ddadb3a47d1087f111abb0245bec2b07…>)
2023-03-03 06:34:19 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:34:19 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:34:34 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:34:34 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:34:51 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:34:51 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:34:52 +0100razetime(~Thunderbi@117.193.1.135)
2023-03-03 06:35:07 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:35:07 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:35:23 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:35:23 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:35:38 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:35:38 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:35:46 +0100 <jackdk> Clinton[m]: hm, true. But if you're going to do that, I'd set things up to let you write multiple useful instances (e.g., accumulate log messages during testing, the "no logging" logger instance, etc.)
2023-03-03 06:35:54 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:35:54 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:36:11 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:36:11 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:36:26 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:36:26 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:36:42 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:36:42 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:36:57 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:36:57 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:37:14 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:37:14 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:37:30 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:37:30 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:37:46 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:37:46 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:38:02 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:38:02 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:38:18 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:38:18 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:38:35 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:38:35 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:38:51 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:38:52 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:39:07 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:39:07 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:39:23 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:39:23 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:39:38 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:39:38 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:39:55 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:39:55 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:40:11 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:40:11 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:40:27 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:40:27 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:40:43 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:40:43 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:40:59 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:40:59 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:41:13 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:41:13 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:41:28 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:41:28 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:41:43 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:41:43 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:41:59 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:41:59 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:42:14 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:42:14 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:42:30 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:42:30 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:42:45 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:42:45 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:43:01 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:43:01 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:43:16 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:43:16 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:43:32 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:43:33 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:43:48 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:43:48 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:44:02 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:44:02 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:44:17 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:44:17 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:44:32 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:44:32 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:44:48 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:44:48 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:45:04 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:45:05 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:45:20 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:45:21 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:45:36 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:45:36 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:45:50 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:45:50 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:46:05 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:46:05 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:46:21 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:46:22 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:46:36 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:46:36 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:46:50 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:46:51 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:47:06 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:47:07 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:47:22 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:47:22 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:47:38 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:47:38 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:47:54 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:47:54 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:48:10 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:48:10 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:48:25 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:48:26 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:48:41 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:48:42 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:48:56 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:48:56 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:49:13 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:49:13 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:49:27 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:49:28 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:49:44 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:49:45 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:50:00 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:50:00 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:50:17 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:50:18 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:50:34 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:50:34 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:50:50 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:50:50 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:51:05 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:51:05 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:51:21 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:51:21 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:51:39 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:51:39 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:51:40 +0100takuan(~takuan@178-116-218-225.access.telenet.be)
2023-03-03 06:51:55 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:51:56 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:52:11 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:52:11 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:52:20 +0100krei-se(~quassel@p5087440b.dip0.t-ipconnect.de)
2023-03-03 06:52:28 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:52:28 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:52:43 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:52:43 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:52:59 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:52:59 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:53:15 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:53:15 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:53:30 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:53:31 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:53:45 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:53:45 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:54:00 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:54:01 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:54:15 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:54:15 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:54:31 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:54:31 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:54:48 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:54:49 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:55:03 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:55:03 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:55:19 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:55:19 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:55:34 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:55:34 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:55:50 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:55:50 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:56:05 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:56:05 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:56:22 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:56:22 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:56:38 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:56:38 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:56:55 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:56:55 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:57:10 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:57:10 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:57:26 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:57:26 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:57:41 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:57:41 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:57:57 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:57:57 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:58:14 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:58:14 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:58:30 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:58:30 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:58:47 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:58:47 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:59:04 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:59:04 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:59:19 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:59:19 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 06:59:34 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:59:34 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 06:59:49 +0100trev(~trev@user/trev)
2023-03-03 06:59:50 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 06:59:50 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:00:06 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:00:06 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:00:21 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:00:21 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:00:35 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:00:35 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:00:50 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:00:50 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:01:05 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:01:05 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:01:21 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:01:21 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:01:36 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:01:36 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:01:52 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:01:52 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:02:05 +0100finsternis(~X@23.226.237.192) (Read error: Connection reset by peer)
2023-03-03 07:02:09 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:02:09 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:02:24 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:02:24 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:02:39 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:02:39 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:02:55 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:02:55 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:03:10 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:03:10 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:03:25 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:03:25 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:03:41 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:03:41 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:03:56 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:03:56 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:04:12 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:04:12 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:04:27 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:04:27 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:04:42 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:04:42 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:04:58 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:04:58 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:05:13 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:05:13 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:05:30 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:05:30 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:05:47 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:05:47 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:06:01 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:06:01 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:06:17 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:06:17 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:06:34 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:06:34 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:06:49 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:06:49 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:07:04 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:07:04 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:07:21 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:07:21 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:07:38 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:07:38 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:07:55 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:07:55 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:08:11 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:08:11 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:08:26 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:08:26 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:08:41 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:08:41 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:08:57 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:08:57 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:09:13 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:09:13 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:09:28 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:09:28 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:09:42 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:09:42 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:09:58 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:09:58 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:10:14 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:10:14 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:10:28 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:10:28 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:10:44 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:10:44 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:11:00 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:11:00 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:11:15 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:11:15 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:11:29 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:11:30 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:11:44 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:11:44 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:12:00 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:12:00 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:12:15 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:12:15 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:12:30 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:12:30 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:12:46 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:12:46 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:13:01 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:13:02 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:13:18 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:13:19 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:13:33 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:13:33 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:13:48 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:13:48 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:14:05 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:14:06 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:14:20 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:14:20 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:14:36 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:14:36 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:14:53 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:14:54 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:15:08 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:15:09 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:15:23 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:15:24 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:15:38 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:15:39 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:15:54 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:15:54 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:16:11 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:16:11 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:16:28 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:16:28 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:16:44 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:16:44 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:17:00 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:17:00 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:17:16 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:17:16 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:17:33 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:17:34 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:17:50 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:17:50 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:18:06 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:18:06 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:18:21 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:18:22 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:18:37 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:18:38 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:18:54 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:18:55 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:19:11 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:19:11 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:19:28 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:19:29 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:19:44 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:19:45 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:19:59 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:19:59 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:20:14 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:20:14 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:20:31 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:20:31 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:20:46 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:20:46 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:21:03 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:21:03 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:21:20 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:21:21 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:21:36 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:21:36 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:21:51 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:21:51 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:22:06 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:22:07 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:22:21 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:22:21 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:22:36 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:22:36 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:22:51 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:22:51 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:23:06 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:23:07 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:23:23 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:23:24 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:23:38 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:23:38 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:23:55 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:23:56 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:24:13 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:24:13 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:24:28 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:24:28 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:24:35 +0100ChanServ+o monochrom
2023-03-03 07:24:45 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:24:46 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:25:01 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:25:02 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Remote host closed the connection)
2023-03-03 07:25:16 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:25:16 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:25:32 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de)
2023-03-03 07:25:33 +0100lambdap237(~lambdap@static.167.190.119.168.clients.your-server.de) (Read error: Connection reset by peer)
2023-03-03 07:25:34 +0100monochrom+b *!*@static.167.190.119.168.clients.your-server.de$##fix_your_connection
2023-03-03 07:25:55 +0100echoreply(~echoreply@45.32.163.16) (Quit: WeeChat 2.8)
2023-03-03 07:26:49 +0100echoreply(~echoreply@45.32.163.16)
2023-03-03 07:26:56 +0100king_gs(~Thunderbi@187.201.41.239)
2023-03-03 07:30:44 +0100razetime(~Thunderbi@117.193.1.135) (Remote host closed the connection)
2023-03-03 07:32:53 +0100razetime(~Thunderbi@117.193.1.135)
2023-03-03 07:33:32 +0100johnw(~johnw@76-234-69-149.lightspeed.frokca.sbcglobal.net)
2023-03-03 07:34:13 +0100monochrom-o monochrom
2023-03-03 07:34:13 +0100jwiegley(~jwiegley@76-234-69-149.lightspeed.frokca.sbcglobal.net)
2023-03-03 07:34:38 +0100harveypwca(~harveypwc@2601:246:c180:a570:3828:d8:e523:3f67)
2023-03-03 07:35:20 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Remote host closed the connection)
2023-03-03 07:35:36 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-03-03 07:46:48 +0100anatta_(~AdiIRC@h-155-4-132-216.NA.cust.bahnhof.se)
2023-03-03 07:47:42 +0100Yumemi_(~Yumemi@chamoin.net)
2023-03-03 07:48:17 +0100Unode_(~Unode@fg-ext-220.embl.de)
2023-03-03 07:48:38 +0100adanwan(~adanwan@gateway/tor-sasl/adanwan) (Ping timeout: 255 seconds)
2023-03-03 07:50:05 +0100adanwan(~adanwan@gateway/tor-sasl/adanwan)
2023-03-03 07:50:57 +0100aku_(~aku@163.172.137.34)
2023-03-03 07:51:46 +0100takuan_dozo(~takuan@178-116-218-225.access.telenet.be)
2023-03-03 07:55:10 +0100 <mauke> oh. I had joins/quits hidden :-)
2023-03-03 07:55:17 +0100takuan(~takuan@178-116-218-225.access.telenet.be) (*.net *.split)
2023-03-03 07:55:17 +0100krei-se(~quassel@p5087440b.dip0.t-ipconnect.de) (*.net *.split)
2023-03-03 07:55:17 +0100use-value(~Thunderbi@2a00:23c6:8a03:2f01:75c2:a71f:beaa:29bf) (*.net *.split)
2023-03-03 07:55:17 +0100mechap(~mechap@user/mechap) (*.net *.split)
2023-03-03 07:55:17 +0100anatta(~AdiIRC@h-155-4-132-216.na.cust.bahnhof.se) (*.net *.split)
2023-03-03 07:55:17 +0100thaumavorio(~thaumavor@thaumavor.io) (*.net *.split)
2023-03-03 07:55:17 +0100infinity0(~infinity0@pwned.gg) (*.net *.split)
2023-03-03 07:55:17 +0100jle`(~jle`@cpe-23-240-75-236.socal.res.rr.com) (*.net *.split)
2023-03-03 07:55:17 +0100jmdaemon(~jmdaemon@user/jmdaemon) (*.net *.split)
2023-03-03 07:55:17 +0100elkcl(~elkcl@broadband-37-110-27-252.ip.moscow.rt.ru) (*.net *.split)
2023-03-03 07:55:17 +0100codaraxis__(~codaraxis@user/codaraxis) (*.net *.split)
2023-03-03 07:55:17 +0100Sgeo(~Sgeo@user/sgeo) (*.net *.split)
2023-03-03 07:55:17 +0100shriekingnoise(~shrieking@186.137.175.87) (*.net *.split)
2023-03-03 07:55:17 +0100ubert(~Thunderbi@p548c9fde.dip0.t-ipconnect.de) (*.net *.split)
2023-03-03 07:55:17 +0100hgolden(~hgolden@cpe-172-251-233-141.socal.res.rr.com) (*.net *.split)
2023-03-03 07:55:17 +0100Franciman(~Franciman@mx1.fracta.dev) (*.net *.split)
2023-03-03 07:55:17 +0100asm(~alexander@user/asm) (*.net *.split)
2023-03-03 07:55:17 +0100phaazon(~phaazon@2001:41d0:a:fe76::1) (*.net *.split)
2023-03-03 07:55:17 +0100bgamari(~bgamari@2a06:a000:b00d::2) (*.net *.split)
2023-03-03 07:55:18 +0100fr33domlover(~fr33domlo@towards.vision) (*.net *.split)
2023-03-03 07:55:18 +0100acarrico(~acarrico@dhcp-68-142-49-163.greenmountainaccess.net) (*.net *.split)
2023-03-03 07:55:18 +0100mixphix(~cigsender@74.124.58.162) (*.net *.split)
2023-03-03 07:55:18 +0100brettgilio(~brettgili@x-irc.gq) (*.net *.split)
2023-03-03 07:55:18 +0100Yumemi(~Yumemi@chamoin.net) (*.net *.split)
2023-03-03 07:55:18 +0100kaskal(~kaskal@089144220250.atnat0029.highway.webapn.at) (*.net *.split)
2023-03-03 07:55:18 +0100quintasan(~quassel@quintasan.pl) (*.net *.split)
2023-03-03 07:55:18 +0100sm[i]_(~user@li229-222.members.linode.com) (*.net *.split)
2023-03-03 07:55:18 +0100ghostbuster(~admin@user/ghostbuster) (*.net *.split)
2023-03-03 07:55:18 +0100aku(~aku@163.172.137.34) (*.net *.split)
2023-03-03 07:55:18 +0100Ekho(~Ekho@user/ekho) (*.net *.split)
2023-03-03 07:55:18 +0100gabiruh_(~gabiruh@vps19177.publiccloud.com.br) (*.net *.split)
2023-03-03 07:55:18 +0100Unode(~Unode@fg-ext-220.embl.de) (*.net *.split)
2023-03-03 07:55:18 +0100kronicma1(user13639@neotame.csclub.uwaterloo.ca) (*.net *.split)
2023-03-03 07:55:18 +0100nullsh(nullsh@user/nexeq) (*.net *.split)
2023-03-03 07:55:18 +0100wrengr(~wrengr@201.59.83.34.bc.googleusercontent.com) (*.net *.split)
2023-03-03 07:55:18 +0100EsoAlgo8(~EsoAlgo@129.146.136.145) (*.net *.split)
2023-03-03 07:55:18 +0100kitzman(~kitzman@user/dekenevs) (*.net *.split)
2023-03-03 07:55:18 +0100AkechiShiro(~licht@user/akechishiro) (*.net *.split)
2023-03-03 07:55:18 +0100krjst(~krjst@2604:a880:800:c1::16b:8001) (*.net *.split)
2023-03-03 07:55:18 +0100sajith(~sajith@user/sajith) (*.net *.split)
2023-03-03 07:55:18 +0100drewolson(~drewolson@user/drewolson) (*.net *.split)
2023-03-03 07:55:23 +0100Unode_Unode
2023-03-03 07:55:27 +0100anatta_anatta
2023-03-03 07:56:00 +0100marienz(~marienz@libera/staff/marienz) (Ping timeout: 615 seconds)
2023-03-03 07:56:54 +0100krei-se(~quassel@p5087440b.dip0.t-ipconnect.de)
2023-03-03 07:56:54 +0100use-value(~Thunderbi@2a00:23c6:8a03:2f01:75c2:a71f:beaa:29bf)
2023-03-03 07:56:54 +0100mechap(~mechap@user/mechap)
2023-03-03 07:56:54 +0100thaumavorio(~thaumavor@thaumavor.io)
2023-03-03 07:56:54 +0100infinity0(~infinity0@pwned.gg)
2023-03-03 07:56:54 +0100jle`(~jle`@cpe-23-240-75-236.socal.res.rr.com)
2023-03-03 07:56:54 +0100jmdaemon(~jmdaemon@user/jmdaemon)
2023-03-03 07:56:54 +0100elkcl(~elkcl@broadband-37-110-27-252.ip.moscow.rt.ru)
2023-03-03 07:56:54 +0100Sgeo(~Sgeo@user/sgeo)
2023-03-03 07:56:54 +0100shriekingnoise(~shrieking@186.137.175.87)
2023-03-03 07:56:54 +0100ubert(~Thunderbi@p548c9fde.dip0.t-ipconnect.de)
2023-03-03 07:56:54 +0100hgolden(~hgolden@cpe-172-251-233-141.socal.res.rr.com)
2023-03-03 07:56:54 +0100Franciman(~Franciman@mx1.fracta.dev)
2023-03-03 07:56:54 +0100asm(~alexander@user/asm)
2023-03-03 07:56:54 +0100phaazon(~phaazon@2001:41d0:a:fe76::1)
2023-03-03 07:56:54 +0100bgamari(~bgamari@2a06:a000:b00d::2)
2023-03-03 07:56:54 +0100fr33domlover(~fr33domlo@towards.vision)
2023-03-03 07:56:54 +0100acarrico(~acarrico@dhcp-68-142-49-163.greenmountainaccess.net)
2023-03-03 07:56:54 +0100mixphix(~cigsender@74.124.58.162)
2023-03-03 07:56:54 +0100brettgilio(~brettgili@x-irc.gq)
2023-03-03 07:56:54 +0100quintasan(~quassel@quintasan.pl)
2023-03-03 07:56:54 +0100sm[i]_(~user@li229-222.members.linode.com)
2023-03-03 07:56:54 +0100ghostbuster(~admin@user/ghostbuster)
2023-03-03 07:56:54 +0100Ekho(~Ekho@user/ekho)
2023-03-03 07:56:54 +0100gabiruh_(~gabiruh@vps19177.publiccloud.com.br)
2023-03-03 07:56:54 +0100kronicma1(user13639@neotame.csclub.uwaterloo.ca)
2023-03-03 07:56:54 +0100nullsh(nullsh@user/nexeq)
2023-03-03 07:56:54 +0100wrengr(~wrengr@201.59.83.34.bc.googleusercontent.com)
2023-03-03 07:56:54 +0100EsoAlgo8(~EsoAlgo@129.146.136.145)
2023-03-03 07:56:54 +0100kitzman(~kitzman@user/dekenevs)
2023-03-03 07:56:54 +0100AkechiShiro(~licht@user/akechishiro)
2023-03-03 07:56:54 +0100krjst(~krjst@2604:a880:800:c1::16b:8001)
2023-03-03 07:56:54 +0100sajith(~sajith@user/sajith)
2023-03-03 07:56:54 +0100drewolson(~drewolson@user/drewolson)
2023-03-03 07:56:56 +0100codaraxis__(~codaraxis@user/codaraxis)
2023-03-03 07:58:51 +0100kaskal(~kaskal@089144220250.atnat0029.highway.webapn.at)
2023-03-03 08:03:08 +0100marienz(~marienz@libera/staff/marienz)
2023-03-03 08:04:41 +0100Sgeo(~Sgeo@user/sgeo) (Read error: Connection reset by peer)
2023-03-03 08:05:06 +0100Sgeo(~Sgeo@user/sgeo)
2023-03-03 08:17:04 +0100king_gs(~Thunderbi@187.201.41.239) (Quit: king_gs)
2023-03-03 08:21:57 +0100Sauvin(~sauvin@user/Sauvin) (Ping timeout: 255 seconds)
2023-03-03 08:32:56 +0100Sauvin(~sauvin@user/Sauvin)
2023-03-03 08:35:31 +0100Bocaneri(~sauvin@user/Sauvin)
2023-03-03 08:35:53 +0100FinnElija(~finn_elij@user/finn-elija/x-0085643) (Ping timeout: 255 seconds)
2023-03-03 08:35:55 +0100BocaneriGuest9469
2023-03-03 08:36:31 +0100SauvinGuest5002
2023-03-03 08:36:31 +0100Guest5002(~sauvin@user/Sauvin) (Killed (copper.libera.chat (Nickname regained by services)))
2023-03-03 08:37:19 +0100Guest9469Sauvin
2023-03-03 08:38:23 +0100FinnElija(~finn_elij@user/finn-elija/x-0085643)
2023-03-03 08:39:08 +0100kenran(~user@user/kenran)
2023-03-03 08:42:39 +0100kenran(~user@user/kenran) (Remote host closed the connection)
2023-03-03 08:44:04 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2023-03-03 08:50:15 +0100ubert(~Thunderbi@p548c9fde.dip0.t-ipconnect.de) (Remote host closed the connection)
2023-03-03 08:50:34 +0100ubert(~Thunderbi@p200300ecdf2947fb8e9b52aeb6f9bd66.dip0.t-ipconnect.de)
2023-03-03 08:54:58 +0100lortabac(~lortabac@2a01:e0a:541:b8f0:d702:c2ed:c3a8:f7e0)
2023-03-03 08:57:04 +0100sammelweis(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Quit: No Ping reply in 180 seconds.)
2023-03-03 08:57:20 +0100shriekingnoise(~shrieking@186.137.175.87) (Ping timeout: 248 seconds)
2023-03-03 08:57:54 +0100mncheckm(~mncheck@193.224.205.254)
2023-03-03 08:58:37 +0100sammelweis(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10)
2023-03-03 09:01:40 +0100acidjnk_new(~acidjnk@p200300d6e715c407a4aad67666d41ab3.dip0.t-ipconnect.de)
2023-03-03 09:05:31 +0100tzh(~tzh@c-24-21-73-154.hsd1.or.comcast.net) (Quit: zzz)
2023-03-03 09:06:32 +0100Sgeo(~Sgeo@user/sgeo) (Read error: Connection reset by peer)
2023-03-03 09:07:17 +0100razetime(~Thunderbi@117.193.1.135) (Ping timeout: 255 seconds)
2023-03-03 09:13:14 +0100FinnElija(~finn_elij@user/finn-elija/x-0085643) (Ping timeout: 255 seconds)
2023-03-03 09:15:07 +0100michalz(~michalz@185.246.204.121)
2023-03-03 09:16:26 +0100kuribas(~user@ptr-17d51engq5fqfsjpte2.18120a2.ip6.access.telenet.be)
2023-03-03 09:18:12 +0100Square(~Square4@user/square) (Ping timeout: 255 seconds)
2023-03-03 09:19:05 +0100 <Hecate> hey hey, I'd like people to chime in on this PR for the presentation of dependencies of the various components of a package in Flora: https://github.com/flora-pm/flora-server/pull/350
2023-03-03 09:19:43 +0100 <Hecate> The "presentation" aspect is the most important, and I'd like to be sure that we offer a path of least resistance for information to be useful
2023-03-03 09:20:44 +0100FinnElija(~finn_elij@user/finn-elija/x-0085643)
2023-03-03 09:22:48 +0100 <[exa]> Hecate: why not list the dependency version constraints too?
2023-03-03 09:23:35 +0100azimut_(~azimut@gateway/tor-sasl/azimut) (Ping timeout: 255 seconds)
2023-03-03 09:24:24 +0100codaraxis___(~codaraxis@user/codaraxis)
2023-03-03 09:27:37 +0100 <Hecate> [exa]: don't ask me, I'm not the person who opened the PR :D Comment in the thread! :)
2023-03-03 09:27:59 +0100razetime(~Thunderbi@117.193.1.135)
2023-03-03 09:28:06 +0100codaraxis__(~codaraxis@user/codaraxis) (Ping timeout: 255 seconds)
2023-03-03 09:30:49 +0100 <[exa]> -ETOOMUCHWORK
2023-03-03 09:31:27 +0100 <Hecate> :(
2023-03-03 09:31:32 +0100 <Hecate> sorry
2023-03-03 09:31:43 +0100instagib[m](~instagibm@2001:470:69fc:105::8156) ()
2023-03-03 09:31:58 +0100 <[exa]> np at all, just, you know :D
2023-03-03 09:32:00 +0100adanwan_(~adanwan@gateway/tor-sasl/adanwan)
2023-03-03 09:32:01 +0100adanwan(~adanwan@gateway/tor-sasl/adanwan) (Quit: _)
2023-03-03 09:32:07 +0100EvanR(~EvanR@user/evanr) (Ping timeout: 260 seconds)
2023-03-03 09:32:15 +0100 <[exa]> btw actual version-version compatibility matrices would be so cool to have somewhere
2023-03-03 09:32:29 +0100 <[exa]> ok this is a good idea that warrants me going there
2023-03-03 09:34:46 +0100eggplantade(~Eggplanta@104-55-37-220.lightspeed.sntcca.sbcglobal.net) (Remote host closed the connection)
2023-03-03 09:38:25 +0100MajorBiscuit(~MajorBisc@c-001-018-056.client.tudelft.eduvpn.nl)
2023-03-03 09:44:30 +0100freeside(~mengwong@103.252.202.85) (Ping timeout: 260 seconds)
2023-03-03 09:45:13 +0100mei(~mei@user/mei)
2023-03-03 09:46:41 +0100kupi(uid212005@id-212005.hampstead.irccloud.com)
2023-03-03 09:50:01 +0100machinedgod(~machinedg@d198-53-218-113.abhsia.telus.net)
2023-03-03 09:50:06 +0100eL_Bart0(eL_Bart0@dietunichtguten.org) (Quit: Restarting)
2023-03-03 09:50:19 +0100eL_Bart0(eL_Bart0@dietunichtguten.org)
2023-03-03 09:51:41 +0100kaol(~kaol@94-237-42-30.nl-ams1.upcloud.host) (Ping timeout: 268 seconds)
2023-03-03 09:51:49 +0100kaol(~kaol@94-237-42-30.nl-ams1.upcloud.host)
2023-03-03 09:56:46 +0100acidjnk_new(~acidjnk@p200300d6e715c407a4aad67666d41ab3.dip0.t-ipconnect.de) (Remote host closed the connection)
2023-03-03 09:57:08 +0100acidjnk_new(~acidjnk@p200300d6e715c407a4aad67666d41ab3.dip0.t-ipconnect.de)
2023-03-03 09:58:10 +0100CiaoSen(~Jura@p200300c9570e91002a3a4dfffe84dbd5.dip0.t-ipconnect.de)
2023-03-03 09:58:18 +0100freeside(~mengwong@103.252.202.85)
2023-03-03 09:58:34 +0100ft(~ft@p3e9bc443.dip0.t-ipconnect.de) (Quit: leaving)
2023-03-03 10:00:06 +0100bigtestaccount[m(~bigtestac@2001:470:69fc:105::2:fae3) (Quit: You have been kicked for being idle)
2023-03-03 10:03:34 +0100bitmapper(uid464869@id-464869.lymington.irccloud.com) (Quit: Connection closed for inactivity)
2023-03-03 10:04:33 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2023-03-03 10:06:50 +0100chele(~chele@user/chele)
2023-03-03 10:07:06 +0100DavidDenoncin[m](~jankoj1ma@2001:470:69fc:105::238)
2023-03-03 10:08:45 +0100vpan(~0@212.117.1.172)
2023-03-03 10:09:40 +0100harveypwca(~harveypwc@2601:246:c180:a570:3828:d8:e523:3f67) (Quit: Leaving)
2023-03-03 10:09:51 +0100cheater_(~Username@user/cheater)
2023-03-03 10:11:10 +0100gnalzo(~gnalzo@2a01:e0a:498:fd50:fcc6:bb5d:489a:ce8c)
2023-03-03 10:12:39 +0100cheater(~Username@user/cheater) (Ping timeout: 268 seconds)
2023-03-03 10:12:47 +0100cheater_cheater
2023-03-03 10:13:14 +0100sammelweis(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Quit: No Ping reply in 180 seconds.)
2023-03-03 10:14:32 +0100sammelweis(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10)
2023-03-03 10:15:45 +0100 <[exa]> tomsmeding: quality photoshop skills
2023-03-03 10:15:52 +0100 <tomsmeding> [exa]: thank you
2023-03-03 10:16:02 +0100 <tomsmeding> the fact that the background is one solid colour makes this much easier though
2023-03-03 10:17:05 +0100merijn(~merijn@86-86-29-250.fixed.kpn.net)
2023-03-03 10:18:34 +0100thaumavorio(~thaumavor@thaumavor.io) (Quit: ZNC 1.8.2 - https://znc.in)
2023-03-03 10:19:28 +0100thaumavorio(~thaumavor@thaumavor.io)
2023-03-03 10:21:07 +0100coot(~coot@2a02:a310:e241:1b00:ec1a:e9df:79ac:66ba)
2023-03-03 10:22:51 +0100Guest76(~Guest76@176.122.87.241)
2023-03-03 10:22:59 +0100 <Guest76> hello
2023-03-03 10:24:15 +0100 <Guest76> trying to use xmlbf library
2023-03-03 10:25:14 +0100 <Guest76> but the compiler throws an error
2023-03-03 10:25:42 +0100 <Guest76> variable not in scope
2023-03-03 10:26:23 +0100 <Guest76> although xmlbf module exports this function
2023-03-03 10:26:52 +0100 <c_wraith> are you looking at the docs for the same version of the library as you are using?
2023-03-03 10:27:01 +0100 <Guest76> yes
2023-03-03 10:27:03 +0100 <Guest76> 0.7
2023-03-03 10:28:44 +0100 <c_wraith> well, then. why not throw a minimal example to reproduce the problem and the error message into a pastebin?
2023-03-03 10:32:03 +0100zeenk(~zeenk@2a02:2f04:a20d:f900::7fe)
2023-03-03 10:32:44 +0100coot_(~coot@2a02:a310:e241:1b00:ec1a:e9df:79ac:66ba)
2023-03-03 10:33:49 +0100 <Guest76> sorry, my mistake. wrong version. thx fro help!
2023-03-03 10:33:55 +0100 <Guest76> *for
2023-03-03 10:35:06 +0100gehmehgeh(~user@user/gehmehgeh)
2023-03-03 10:35:14 +0100eggplantade(~Eggplanta@104-55-37-220.lightspeed.sntcca.sbcglobal.net)
2023-03-03 10:35:34 +0100coot(~coot@2a02:a310:e241:1b00:ec1a:e9df:79ac:66ba) (Ping timeout: 265 seconds)
2023-03-03 10:35:34 +0100coot_coot
2023-03-03 10:38:12 +0100jpds(~jpds@gateway/tor-sasl/jpds) (Remote host closed the connection)
2023-03-03 10:39:19 +0100jpds(~jpds@gateway/tor-sasl/jpds)
2023-03-03 10:39:29 +0100eggplantade(~Eggplanta@104-55-37-220.lightspeed.sntcca.sbcglobal.net) (Ping timeout: 246 seconds)
2023-03-03 10:39:33 +0100ix(~ix@213.205.242.28)
2023-03-03 10:43:38 +0100enoq(~enoq@2a05:1141:1f5:5600:b9c9:721a:599:bfe7)
2023-03-03 10:53:55 +0100Guest76(~Guest76@176.122.87.241) (Quit: Client closed)
2023-03-03 10:55:26 +0100teo(~teo@user/teo)
2023-03-03 10:57:31 +0100freeside(~mengwong@103.252.202.85) (Ping timeout: 248 seconds)
2023-03-03 10:57:44 +0100 <tomsmeding> Hecate: in what way is <details> suboptimal for screen readers? I know nothing of that domain but I'd have expected it to be fine, because it's just simple, standardised html, without any JS
2023-03-03 11:00:30 +0100gurkenglas(~gurkengla@dynamic-046-114-178-010.46.114.pool.telefonica.de)
2023-03-03 11:03:13 +0100xff0x(~xff0x@125x103x176x34.ap125.ftth.ucom.ne.jp) (Ping timeout: 268 seconds)
2023-03-03 11:03:15 +0100 <Hecate> tomsmeding: JS is far to be the problem we think it is for screen readers
2023-03-03 11:03:29 +0100 <Hecate> especially when you try and replace it with CSS tricks for interactivity
2023-03-03 11:03:46 +0100 <Hecate> tomsmeding: JS can insert aria labels in html tags dynamically
2023-03-03 11:04:12 +0100 <tomsmeding> fair point
2023-03-03 11:04:21 +0100hgolden_(~hgolden@cpe-172-251-233-141.socal.res.rr.com)
2023-03-03 11:05:03 +0100 <tomsmeding> Hecate: would replacing the <details> with JS improve the situation? I would expect no, but maybe you know better
2023-03-03 11:05:51 +0100ix(~ix@213.205.242.28) (Ping timeout: 248 seconds)
2023-03-03 11:05:51 +0100hgolden(~hgolden@cpe-172-251-233-141.socal.res.rr.com) (Ping timeout: 248 seconds)
2023-03-03 11:06:43 +0100__monty__(~toonn@user/toonn)
2023-03-03 11:06:53 +0100krei-se(~quassel@p5087440b.dip0.t-ipconnect.de) (Remote host closed the connection)
2023-03-03 11:07:01 +0100 <Hecate> https://www.scottohara.me/blog/2018/09/03/details-and-summary.html
2023-03-03 11:07:06 +0100 <Hecate> https://blog.learningtoo.eu/expanding-summary-details-accessibly
2023-03-03 11:07:16 +0100 <Hecate> https://www.hassellinclusion.com/blog/accessible-accordions-part-2-using-details-summary/
2023-03-03 11:07:42 +0100kenran(~user@user/kenran)
2023-03-03 11:11:38 +0100mc47(~mc47@xmonad/TheMC47)
2023-03-03 11:11:59 +0100cfricke(~cfricke@user/cfricke)
2023-03-03 11:14:53 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2023-03-03 11:20:26 +0100gehmehgeh(~user@user/gehmehgeh) (Remote host closed the connection)
2023-03-03 11:28:56 +0100 <Hecate> tomsmeding: note also that it's a very hard topic and with very little knowledge "out there"
2023-03-03 11:29:19 +0100Guest372(~Guest37@2600:4041:4527:3b00:5dae:3b03:d192:c7db)
2023-03-03 11:29:40 +0100Guest372(~Guest37@2600:4041:4527:3b00:5dae:3b03:d192:c7db) (Client Quit)
2023-03-03 11:29:56 +0100Guest3781(~Guest37@2600:4041:4527:3b00:5dae:3b03:d192:c7db)
2023-03-03 11:30:28 +0100 <shryke> These three links are quite outdated by the standards of modern browsers and software
2023-03-03 11:31:05 +0100npmania(~Thunderbi@91.193.7.46)
2023-03-03 11:32:02 +0100 <Hecate> shryke: and you are… ?
2023-03-03 11:32:08 +0100 <Hecate> any kind of web platform developer?
2023-03-03 11:32:15 +0100 <Hecate> or an expert in the web platform?
2023-03-03 11:32:24 +0100 <Hecate> or just trolling?
2023-03-03 11:32:49 +0100 <shryke> Then again, I do not know the impact of the condition "it should work on browsers that people use" - for all I know the majority of people using these accessibilty features indeed use the versions tested in these links
2023-03-03 11:33:33 +0100 <shryke> Hecate: that was uncalled for.
2023-03-03 11:34:18 +0100npmania1(~Thunderbi@45.8.223.224)
2023-03-03 11:34:40 +0100 <shryke> I am merely curious whether you have similar relevant studies done on more recent versions of browsers and assistant software
2023-03-03 11:34:42 +0100 <Hecate> shryke: no no, I just value my time and don't take that kind of remark like yours from total strangers
2023-03-03 11:35:39 +0100 <Hecate> the last stable release of the JAWS screen reader was in 2020
2023-03-03 11:35:43 +0100npmania(~Thunderbi@91.193.7.46) (Ping timeout: 248 seconds)
2023-03-03 11:35:44 +0100npmania1npmania
2023-03-03 11:35:54 +0100 <shryke> Hecate: whatever. Please keep being toxic.
2023-03-03 11:36:11 +0100 <Hecate> 👍 ok
2023-03-03 11:37:33 +0100 <[exa]> shryke: btw anything specifically newer out there?
2023-03-03 11:42:09 +0100econo(uid147250@user/econo) (Quit: Connection closed for inactivity)
2023-03-03 11:43:04 +0100razetime(~Thunderbi@117.193.1.135) (Remote host closed the connection)
2023-03-03 11:43:14 +0100shryke(~shryke@2a00:4b00:13c:cc:b27b:25ff:fe18:efd) (Quit: WeeChat 3.8)
2023-03-03 11:44:47 +0100ubert1(~Thunderbi@2a02:8109:abc0:6434:a35b:2d28:c16d:4824)
2023-03-03 11:51:40 +0100gurkenglas(~gurkengla@dynamic-046-114-178-010.46.114.pool.telefonica.de) (Ping timeout: 252 seconds)
2023-03-03 11:53:31 +0100gurkenglas(~gurkengla@dynamic-046-114-178-010.46.114.pool.telefonica.de)
2023-03-03 11:56:32 +0100jmdaemon(~jmdaemon@user/jmdaemon) (Ping timeout: 248 seconds)
2023-03-03 11:57:10 +0100gnalzo(~gnalzo@2a01:e0a:498:fd50:fcc6:bb5d:489a:ce8c) (Quit: WeeChat 3.8)
2023-03-03 12:05:50 +0100cheater_(~Username@user/cheater)
2023-03-03 12:06:31 +0100jpds(~jpds@gateway/tor-sasl/jpds) (Remote host closed the connection)
2023-03-03 12:06:47 +0100jpds(~jpds@gateway/tor-sasl/jpds)
2023-03-03 12:08:18 +0100cheater(~Username@user/cheater) (Ping timeout: 255 seconds)
2023-03-03 12:08:26 +0100cheater_cheater
2023-03-03 12:09:13 +0100beteigeuze(~Thunderbi@a79-169-109-107.cpe.netcabo.pt)
2023-03-03 12:09:43 +0100npmania1(~Thunderbi@138.199.60.27)
2023-03-03 12:09:47 +0100npmania(~Thunderbi@45.8.223.224) (Ping timeout: 264 seconds)
2023-03-03 12:09:48 +0100npmania1npmania
2023-03-03 12:09:51 +0100acidjnk_new(~acidjnk@p200300d6e715c407a4aad67666d41ab3.dip0.t-ipconnect.de) (Ping timeout: 248 seconds)
2023-03-03 12:10:53 +0100acidjnk_new(~acidjnk@p200300d6e715c407a4aad67666d41ab3.dip0.t-ipconnect.de)
2023-03-03 12:13:09 +0100Guest3781(~Guest37@2600:4041:4527:3b00:5dae:3b03:d192:c7db) (Quit: Client closed)
2023-03-03 12:15:51 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 255 seconds)
2023-03-03 12:19:02 +0100anpad(~pandeyan@user/anpad) (Read error: Connection reset by peer)
2023-03-03 12:19:11 +0100npmania(~Thunderbi@138.199.60.27) (Ping timeout: 260 seconds)
2023-03-03 12:19:50 +0100 <ph88> Can i use this library https://hackage.haskell.org/package/validation-1.1.2/docs/Data-Validation.html with applicative do? which function can i use to write multiple failures?
2023-03-03 12:20:27 +0100merijn(~merijn@86-86-29-250.fixed.kpn.net) (Ping timeout: 265 seconds)
2023-03-03 12:21:17 +0100anpad(~pandeyan@user/anpad)
2023-03-03 12:22:08 +0100merijn(~merijn@86-86-29-250.fixed.kpn.net)
2023-03-03 12:27:54 +0100jespada(~jespada@cpc121308-nmal25-2-0-cust15.19-2.cable.virginm.net) (Remote host closed the connection)
2023-03-03 12:28:35 +0100jespada(~jespada@cpc121308-nmal25-2-0-cust15.19-2.cable.virginm.net)
2023-03-03 12:40:48 +0100mmhat(~mmh@p200300f1c70de84aee086bfffe095315.dip0.t-ipconnect.de)
2023-03-03 12:41:09 +0100enoq(~enoq@2a05:1141:1f5:5600:b9c9:721a:599:bfe7) (Remote host closed the connection)
2023-03-03 12:44:29 +0100gurkenglas(~gurkengla@dynamic-046-114-178-010.46.114.pool.telefonica.de) (Quit: Lost terminal)
2023-03-03 12:44:56 +0100gurkenglas(~gurkengla@dynamic-046-114-178-010.46.114.pool.telefonica.de)
2023-03-03 12:46:42 +0100o-90(~o-90@gateway/tor-sasl/o-90)
2023-03-03 12:47:46 +0100 <jackdk> I recommend validation-selective over validation because its semigroup operation is more often what you want
2023-03-03 12:48:09 +0100o-90(~o-90@gateway/tor-sasl/o-90) (Remote host closed the connection)
2023-03-03 12:48:30 +0100coot(~coot@2a02:a310:e241:1b00:ec1a:e9df:79ac:66ba) (Quit: coot)
2023-03-03 12:49:07 +0100coot(~coot@2a02:a310:e241:1b00:ec1a:e9df:79ac:66ba)
2023-03-03 12:50:57 +0100mrcsno(~mrcsno@user/mrcsno) (Quit: WeeChat 3.5)
2023-03-03 12:52:59 +0100mmhat(~mmh@p200300f1c70de84aee086bfffe095315.dip0.t-ipconnect.de) (Quit: WeeChat 3.8)
2023-03-03 12:54:15 +0100 <ph88> jackdk, what about the semigroup operation is more often what you want? I can't really spot the difference https://github.com/system-f/validation/blob/master/src/Data/Validation.hs#L98-L104 https://github.com/kowainik/validation-selective/blob/main/src/Validation.hs#L463-L467
2023-03-03 12:56:07 +0100 <[exa]> ph88: more likely https://github.com/system-f/validation/blob/master/src/Data/Validation.hs#L172 vs https://github.com/kowainik/validation-selective/blob/main/src/Validation.hs#L398
2023-03-03 12:57:51 +0100 <jackdk> yes, I would prefer semigroup to combine validations "semigroupally". If I want "take the first passing" semantics, I can then explicitly use a `First` newtype
2023-03-03 12:58:02 +0100acidjnk_new(~acidjnk@p200300d6e715c407a4aad67666d41ab3.dip0.t-ipconnect.de) (Remote host closed the connection)
2023-03-03 12:58:26 +0100acidjnk_new(~acidjnk@p200300d6e715c407a4aad67666d41ab3.dip0.t-ipconnect.de)
2023-03-03 12:58:35 +0100ccapndave(~ccapndave@xcpe-62-167-164-99.cgn.res.adslplus.ch)
2023-03-03 12:59:11 +0100 <ph88> in the validation library doesn't it combine ?
2023-03-03 13:04:11 +0100 <jackdk> No, it "takes the first" on success but combines on error. You can tell this by the absence of a `Semigroup a` constraint, which is why I prefer `validation-selective`
2023-03-03 13:04:59 +0100masterbuilder(~masterbui@user/masterbuilder) (Ping timeout: 248 seconds)
2023-03-03 13:05:11 +0100masterbuilder(~masterbui@user/masterbuilder)
2023-03-03 13:05:30 +0100 <ph88> jackdk, you mean if multiple succeed then it quits early ?
2023-03-03 13:08:36 +0100xff0x(~xff0x@2405:6580:b080:900:aac1:e87d:31c4:e76)
2023-03-03 13:12:47 +0100masterbuilder(~masterbui@user/masterbuilder) (Ping timeout: 248 seconds)
2023-03-03 13:14:30 +0100 <jackdk> no
2023-03-03 13:14:34 +0100masterbuilder(~masterbui@user/masterbuilder)
2023-03-03 13:15:21 +0100 <jackdk> given v1, v2 :: Validaiton e a, I would prefer v1 <> v2 to contain the (<>) applied to both 'a's (if both succeeded)
2023-03-03 13:15:44 +0100 <jackdk> maybe that's what you were saying, it's late here
2023-03-03 13:19:34 +0100ccapndave(~ccapndave@xcpe-62-167-164-99.cgn.res.adslplus.ch) (Quit: My MacBook has gone to sleep. ZZZzzz…)
2023-03-03 13:19:53 +0100 <ph88> jackdk, i think we understood each other :p
2023-03-03 13:20:02 +0100 <ph88> what's your timezone ?
2023-03-03 13:21:04 +0100use-value(~Thunderbi@2a00:23c6:8a03:2f01:75c2:a71f:beaa:29bf) (Remote host closed the connection)
2023-03-03 13:21:05 +0100krei-se(~quassel@p5087440b.dip0.t-ipconnect.de)
2023-03-03 13:21:24 +0100use-value(~Thunderbi@2a00:23c6:8a03:2f01:75c2:a71f:beaa:29bf)
2023-03-03 13:26:52 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8) (Remote host closed the connection)
2023-03-03 13:33:00 +0100albet70(~xxx@2400:8902::f03c:92ff:fe60:98d8)
2023-03-03 13:33:03 +0100L29Ah(~L29Ah@wikipedia/L29Ah)
2023-03-03 13:33:06 +0100 <[exa]> UTC+late
2023-03-03 13:36:06 +0100cfricke(~cfricke@user/cfricke) (Quit: WeeChat 3.8)
2023-03-03 13:36:07 +0100krei-se(~quassel@p5087440b.dip0.t-ipconnect.de) (Remote host closed the connection)
2023-03-03 13:36:39 +0100akegalj(~akegalj@93-138-62-24.adsl.net.t-com.hr)
2023-03-03 13:38:25 +0100xff0x(~xff0x@2405:6580:b080:900:aac1:e87d:31c4:e76) (Ping timeout: 260 seconds)
2023-03-03 13:38:29 +0100bontaq(~user@ool-45779fe5.dyn.optonline.net)
2023-03-03 13:38:47 +0100xff0x(~xff0x@ai081074.d.east.v6connect.net)
2023-03-03 13:42:35 +0100segfaultfizzbuzz(~segfaultf@23-93-74-212.fiber.dynamic.sonic.net)
2023-03-03 13:48:50 +0100Guest3711(~Guest37@2600:4041:4527:3b00:5dae:3b03:d192:c7db)
2023-03-03 13:55:34 +0100jero98772(~jero98772@2800:484:1d80:d8ce:efcc:cbb3:7f2a:6dff)
2023-03-03 13:57:04 +0100use-value1(~Thunderbi@2a00:23c6:8a03:2f01:6932:2b9:8e68:7497)
2023-03-03 13:59:43 +0100use-value(~Thunderbi@2a00:23c6:8a03:2f01:75c2:a71f:beaa:29bf) (Ping timeout: 248 seconds)
2023-03-03 14:01:05 +0100use-value1(~Thunderbi@2a00:23c6:8a03:2f01:6932:2b9:8e68:7497) (Ping timeout: 246 seconds)
2023-03-03 14:02:54 +0100use-value(~Thunderbi@2a00:23c6:8a03:2f01:61da:7e50:a55e:adda)
2023-03-03 14:08:35 +0100pavonia(~user@user/siracusa) (Quit: Bye!)
2023-03-03 14:09:16 +0100use-value(~Thunderbi@2a00:23c6:8a03:2f01:61da:7e50:a55e:adda) (Quit: use-value)
2023-03-03 14:09:31 +0100acidjnk_new(~acidjnk@p200300d6e715c407a4aad67666d41ab3.dip0.t-ipconnect.de) (Ping timeout: 248 seconds)
2023-03-03 14:12:30 +0100azimut(~azimut@gateway/tor-sasl/azimut)
2023-03-03 14:13:42 +0100azimut(~azimut@gateway/tor-sasl/azimut) (Remote host closed the connection)
2023-03-03 14:14:16 +0100azimut(~azimut@gateway/tor-sasl/azimut)
2023-03-03 14:16:03 +0100use-value(~Thunderbi@2a00:23c6:8a03:2f01:61da:7e50:a55e:adda)
2023-03-03 14:18:17 +0100use-value(~Thunderbi@2a00:23c6:8a03:2f01:61da:7e50:a55e:adda) (Client Quit)
2023-03-03 14:20:22 +0100cfricke(~cfricke@user/cfricke)
2023-03-03 14:21:33 +0100use-value(~Thunderbi@2a00:23c6:8a03:2f01:61da:7e50:a55e:adda)
2023-03-03 14:25:50 +0100terrorjack(~terrorjac@2a01:4f8:1c1e:4e8c::) (Quit: The Lounge - https://thelounge.chat)
2023-03-03 14:27:15 +0100terrorjack(~terrorjac@2a01:4f8:1c1e:4e8c::)
2023-03-03 14:29:09 +0100hugo-(znc@verdigris.lysator.liu.se) (Ping timeout: 255 seconds)
2023-03-03 14:33:36 +0100terrorjack(~terrorjac@2a01:4f8:1c1e:4e8c::) (Quit: The Lounge - https://thelounge.chat)
2023-03-03 14:36:15 +0100hugo-(znc@verdigris.lysator.liu.se)
2023-03-03 14:37:12 +0100segfaultfizzbuzz(~segfaultf@23-93-74-212.fiber.dynamic.sonic.net) (Ping timeout: 268 seconds)
2023-03-03 14:38:56 +0100eggplantade(~Eggplanta@2600:1700:38c5:d800:e1f4:8ede:df26:d4a0)
2023-03-03 14:42:10 +0100vglfr(~vglfr@145.224.100.65) (Read error: Connection reset by peer)
2023-03-03 14:42:28 +0100vglfr(~vglfr@145.224.100.65)
2023-03-03 14:42:58 +0100jespada(~jespada@cpc121308-nmal25-2-0-cust15.19-2.cable.virginm.net) (Quit: Textual IRC Client: www.textualapp.com)
2023-03-03 14:43:45 +0100eggplantade(~Eggplanta@2600:1700:38c5:d800:e1f4:8ede:df26:d4a0) (Ping timeout: 260 seconds)
2023-03-03 14:45:43 +0100cfricke(~cfricke@user/cfricke) (Ping timeout: 260 seconds)
2023-03-03 14:49:27 +0100L29Ah(~L29Ah@wikipedia/L29Ah) ()
2023-03-03 14:54:08 +0100CiaoSen(~Jura@p200300c9570e91002a3a4dfffe84dbd5.dip0.t-ipconnect.de) (Ping timeout: 248 seconds)
2023-03-03 15:02:53 +0100jpds(~jpds@gateway/tor-sasl/jpds) (Ping timeout: 255 seconds)
2023-03-03 15:05:41 +0100jpds(~jpds@gateway/tor-sasl/jpds)
2023-03-03 15:10:22 +0100 <dminuoso_> % case ("foo" :: T.Text) of "foo" -> ()
2023-03-03 15:10:22 +0100 <yahb2> ()
2023-03-03 15:10:30 +0100 <dminuoso_> How does this work?
2023-03-03 15:11:26 +0100jpds(~jpds@gateway/tor-sasl/jpds) (Ping timeout: 255 seconds)
2023-03-03 15:11:38 +0100 <merijn> dminuoso_: Same as numeric literals, via Eq
2023-03-03 15:12:24 +0100 <dminuoso_> Where is that behavior documented?
2023-03-03 15:12:27 +0100 <merijn> :t let foo 1 = () in foo
2023-03-03 15:12:28 +0100 <lambdabot> (Eq a, Num a) => a -> ()
2023-03-03 15:12:32 +0100 <merijn> Note the Eq constraint
2023-03-03 15:12:36 +0100 <dminuoso_> Mmm
2023-03-03 15:12:45 +0100 <merijn> eh..."somewhere"?
2023-03-03 15:12:48 +0100 <dminuoso_> Heh.
2023-03-03 15:12:57 +0100 <merijn> OverloadedStrings, probably?
2023-03-03 15:12:58 +0100 <dminuoso_> I feel like this should be documented in the OverloadedStrings extension
2023-03-03 15:13:00 +0100 <dminuoso_> Yeah but its not
2023-03-03 15:13:19 +0100 <dminuoso_> Oh hold on
2023-03-03 15:13:24 +0100vulpine(xfnw@tilde.team) (Quit: Connection reset by purr)
2023-03-03 15:13:25 +0100 <dminuoso_> Its subtly mentioned at the end doh.
2023-03-03 15:13:27 +0100 <dminuoso_> `Note that deriving Eq is necessary for the pattern matching to work since it gets translated into an equality comparison.`
2023-03-03 15:13:38 +0100 <dminuoso_> Okay I see. Thanks merijn
2023-03-03 15:13:38 +0100 <merijn> "If used in a pattern the literal will be replaced by an equality test, in the same way as an integer literal is."
2023-03-03 15:13:50 +0100 <dminuoso_> merijn: Uh I fail at reading I guess.
2023-03-03 15:13:56 +0100 <merijn> That's like, the 2nd paragraph :p
2023-03-03 15:15:29 +0100gnalzo(~gnalzo@2a01:e0a:498:fd50:fcc6:bb5d:489a:ce8c)
2023-03-03 15:16:18 +0100 <dminuoso_> I was visually scanning for something more prominent
2023-03-03 15:19:27 +0100sammelweis(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Ping timeout: 255 seconds)
2023-03-03 15:19:32 +0100thegeekinside(~thegeekin@189.141.115.134)
2023-03-03 15:19:34 +0100sammelweis(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10)
2023-03-03 15:21:18 +0100vulpine(xfnw@tilde.team)
2023-03-03 15:21:41 +0100mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2023-03-03 15:26:46 +0100jpds(~jpds@gateway/tor-sasl/jpds)
2023-03-03 15:27:36 +0100ix(~ix@213.205.242.28)
2023-03-03 15:33:21 +0100ix(~ix@213.205.242.28) (Read error: Connection reset by peer)
2023-03-03 15:37:31 +0100kenran(~user@user/kenran) (Remote host closed the connection)
2023-03-03 15:38:02 +0100gurkenglas(~gurkengla@dynamic-046-114-178-010.46.114.pool.telefonica.de) (Ping timeout: 246 seconds)
2023-03-03 15:39:08 +0100ix(~ix@213.205.242.28)
2023-03-03 15:40:02 +0100gurkenglas(~gurkengla@dynamic-046-114-176-169.46.114.pool.telefonica.de)
2023-03-03 15:43:06 +0100ix(~ix@213.205.242.28) (Read error: Connection reset by peer)
2023-03-03 15:48:22 +0100ix(~ix@213.205.242.28)
2023-03-03 15:50:18 +0100shriekingnoise(~shrieking@186.137.175.87)
2023-03-03 15:52:14 +0100kenran(~user@user/kenran)
2023-03-03 15:53:24 +0100 <kenran> I'm a little overwhelmed by the following error I get in a transitive dependency: https://paste.systemli.org/?24b2180b0057eac8#pXs5TEK42dbQMZF9L8yLA7f9WAJhRg4PZE18t4ZJkcx
2023-03-03 15:53:25 +0100ix(~ix@213.205.242.28) (Read error: Connection reset by peer)
2023-03-03 15:53:30 +0100 <kenran> Can anyone of you point me in a direction?
2023-03-03 15:55:04 +0100 <geekosaur> ugh, lens errors
2023-03-03 15:55:37 +0100 <geekosaur> they're very powerful, but the error messages will make you claw your eyes out
2023-03-03 15:55:43 +0100acidjnk_new(~acidjnk@p200300d6e715c407c95a74b02ab5f24e.dip0.t-ipconnect.de)
2023-03-03 15:57:24 +0100pdw(~user@197.33.187.81.in-addr.arpa)
2023-03-03 15:59:47 +0100ix(~ix@213.205.242.28)
2023-03-03 16:00:49 +0100 <kenran> yeah, and by looking at the code I don't see anything that should not work, nor do I see which package update could have led to this error. My boss had an idea about making the function non-point-free anymore, which I'm going to try out next.
2023-03-03 16:03:01 +0100lortabac(~lortabac@2a01:e0a:541:b8f0:d702:c2ed:c3a8:f7e0) (Quit: WeeChat 2.8)
2023-03-03 16:04:37 +0100 <kenran> I mean, it's about the function outputIxAt :: OutputIx -> Lens' (IntMap v) (Maybe v), where outputIxAt = intAt . unOutputIx, and the latter is a newtype accessor yielding an Int, the former has the signature Int -> Lens' (IntMap v) (Maybe v)...
2023-03-03 16:06:57 +0100kupiDiscord2IRC
2023-03-03 16:07:33 +0100Me-me(~me-me@2602:ff16:3:0:1:dc:beef:d00d) (Remote host closed the connection)
2023-03-03 16:07:54 +0100robobub(uid248673@id-248673.uxbridge.irccloud.com) (Quit: Connection closed for inactivity)
2023-03-03 16:08:21 +0100Me-me(~me-me@2602:ff16:3:0:1:dc:beef:d00d)
2023-03-03 16:08:42 +0100Me-me(~me-me@2602:ff16:3:0:1:dc:beef:d00d) (Remote host closed the connection)
2023-03-03 16:09:29 +0100califax(~califax@user/califx) (Ping timeout: 255 seconds)
2023-03-03 16:09:39 +0100Discord2IRCkupi
2023-03-03 16:09:41 +0100Me-me(~me-me@2602:ff16:3:0:1:dc:beef:d00d)
2023-03-03 16:09:56 +0100califax(~califax@user/califx)
2023-03-03 16:10:11 +0100chexum(~quassel@gateway/tor-sasl/chexum) (Remote host closed the connection)
2023-03-03 16:10:31 +0100chexum(~quassel@gateway/tor-sasl/chexum)
2023-03-03 16:14:41 +0100dekster(~dekster@2603-7000-1203-4d7c-8c00-75d6-3287-dba1.res6.spectrum.com)
2023-03-03 16:15:22 +0100 <kenran> that indeed made the second error go away; now there's only the the one at 'at' left... but time for the weekend :)
2023-03-03 16:15:23 +0100gnalzo(~gnalzo@2a01:e0a:498:fd50:fcc6:bb5d:489a:ce8c) (Quit: WeeChat 3.8)
2023-03-03 16:15:47 +0100califax(~califax@user/califx) (Ping timeout: 255 seconds)
2023-03-03 16:16:59 +0100raym(~ray@user/raym) (Ping timeout: 248 seconds)
2023-03-03 16:17:26 +0100califax(~califax@user/califx)
2023-03-03 16:19:39 +0100 <kenran> holy shit, that was really it... I had to replace two dots with dollars further up, and then it worked as well
2023-03-03 16:20:07 +0100jmdaemon(~jmdaemon@user/jmdaemon)
2023-03-03 16:20:45 +0100Guest3711(~Guest37@2600:4041:4527:3b00:5dae:3b03:d192:c7db) (Quit: Client closed)
2023-03-03 16:20:51 +0100Axman6(~Axman6@user/axman6) (Ping timeout: 240 seconds)
2023-03-03 16:24:04 +0100raym(~ray@user/raym)
2023-03-03 16:26:18 +0100CiaoSen(~Jura@p200300c9570e91002a3a4dfffe84dbd5.dip0.t-ipconnect.de)
2023-03-03 16:31:11 +0100freeside(~mengwong@103.252.202.85)
2023-03-03 16:33:19 +0100jmdaemon(~jmdaemon@user/jmdaemon) (Ping timeout: 252 seconds)
2023-03-03 16:33:21 +0100k8yun(~k8yun@user/k8yun)
2023-03-03 16:33:45 +0100 <pdw> kenran: nice - always satisfying when that sort of things clicks :-)
2023-03-03 16:33:57 +0100bontaq(~user@ool-45779fe5.dyn.optonline.net) (Remote host closed the connection)
2023-03-03 16:36:11 +0100ubert(~Thunderbi@p200300ecdf2947fb8e9b52aeb6f9bd66.dip0.t-ipconnect.de) (Ping timeout: 248 seconds)
2023-03-03 16:36:11 +0100ubert1ubert
2023-03-03 16:36:23 +0100 <pdw> Have a few questions about using an 'integer-simple' GHC
2023-03-03 16:36:36 +0100 <pdw> Presume this is a sensible place to ask
2023-03-03 16:36:36 +0100ub(~Thunderbi@p200300ecdf29471416a399119c633262.dip0.t-ipconnect.de)
2023-03-03 16:36:48 +0100 <merijn> Depends on how complicated your questions are ;)
2023-03-03 16:36:57 +0100 <geekosaur> don't ask to ask, just ask 🙂 (not that I can necessarily help)
2023-03-03 16:37:11 +0100 <pdw> Sure - will do. Still typing!
2023-03-03 16:37:33 +0100 <pdw> Is there an easier way to get hold of a non-libGMP build of GHC than building from source?
2023-03-03 16:37:49 +0100 <pdw> I see the Alpine builds are integer-simple, but others aren't.
2023-03-03 16:38:08 +0100gurkenglas(~gurkengla@dynamic-046-114-176-169.46.114.pool.telefonica.de) (Ping timeout: 248 seconds)
2023-03-03 16:38:17 +0100 <pdw> ... and b) Is building from source comparatively straightforward compared to building other tools (e.g. Emacs) from source?
2023-03-03 16:38:54 +0100 <geekosaur> not currently. they want to make the integer impl runtime selectable in the future, but currently that's not possible
2023-03-03 16:38:56 +0100 <merijn> pdw: I haven't build emacs, but it's pretty straightforward (if time consuming)
2023-03-03 16:39:15 +0100 <pdw> ah, good news
2023-03-03 16:39:19 +0100 <geekosaur> ghc can be a pain to build from sourc4e but iirc ghcup can do it for you these days
2023-03-03 16:39:27 +0100 <merijn> pdw: there's no realy tricky dependencies to wrangle, since most stuff is in tree
2023-03-03 16:39:39 +0100 <merijn> geekosaur: I mean, that's mostly in weird configurations and cross compiling scenarios
2023-03-03 16:39:44 +0100 <geekosaur> yeh
2023-03-03 16:39:46 +0100 <maerwald> geekosaur: well, the make-hadrian move didn't make all that easier
2023-03-03 16:39:58 +0100 <maerwald> it's a maze of bugs you have to navigate
2023-03-03 16:40:03 +0100 <pdw> Does using an integer-simple build open up any other cans of worms (e.g. packages not working when cabal installs default versions or something?)
2023-03-03 16:40:04 +0100 <merijn> If you have access to a "normal" GHC in your environment then your only real dependencies are regular C tools
2023-03-03 16:40:21 +0100 <geekosaur> integer-simple should be a drop-in replacement
2023-03-03 16:40:21 +0100 <merijn> pdw: It should "Just Work" although possibly less efficient
2023-03-03 16:40:41 +0100 <geekosaur> it's conceivable that there are packages that depend on gmp being wired in, but those should be rare
2023-03-03 16:41:14 +0100 <geekosaur> and the rewritten integer-simple backend is pretty comparable to gmp these days
2023-03-03 16:41:21 +0100 <pdw> merijn/geekosaur: Thanks. Not doing anything that's efficiency-sensitive, so sounds like a good way to go.
2023-03-03 16:41:44 +0100 <pdw> Building on Windows is done with MSYS2?
2023-03-03 16:42:10 +0100 <geekosaur> yes
2023-03-03 16:44:26 +0100gurkenglas(~gurkengla@dynamic-046-114-176-169.46.114.pool.telefonica.de)
2023-03-03 16:45:55 +0100 <pdw> I like the sound of selecting the integer backend at runtime
2023-03-03 16:46:18 +0100 <pdw> Is the idea that you'd pass a build flag/Cabal setting to make the build use one or the other?
2023-03-03 16:47:14 +0100 <geekosaur> I think it's intended to be an RTS setting (+RTS …)
2023-03-03 16:47:22 +0100 <merijn> It can't be, right?
2023-03-03 16:47:36 +0100 <geekosaur> the first stage (making them use compatible representations) is already done
2023-03-03 16:47:39 +0100 <merijn> That'd require some indirection at runtime on every math op
2023-03-03 16:47:57 +0100 <merijn> That'd wreck performance. Seems much more sensical for it to be a compile time option?
2023-03-03 16:48:16 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2023-03-03 16:48:17 +0100use-value(~Thunderbi@2a00:23c6:8a03:2f01:61da:7e50:a55e:adda) (Quit: use-value)
2023-03-03 16:48:26 +0100 <geekosaur> all the stuff I've seen says runtime. I'm not sure it makes sense either, tbh
2023-03-03 16:48:54 +0100 <merijn> geekosaur: Well, there's "at GHC runtime" vs "at program runtime"
2023-03-03 16:49:14 +0100 <merijn> the former makes sense
2023-03-03 16:49:22 +0100 <geekosaur> not only for technical reasons but also because I imagine the folks who want to use simple instead of gmp won't want to switch dynamically but always use one or the other
2023-03-03 16:49:48 +0100 <geekosaur> ](since it's usually driven by "avoid anything related to GPL for lawyer reasons")
2023-03-03 16:49:59 +0100 <merijn> *LGPL ;)
2023-03-03 16:50:17 +0100 <geekosaur> either. lawyers don't generally distinguish
2023-03-03 16:52:51 +0100 <pdw> Main difference (IIRC) is you can link proprietary tools with LGPL libraries, so long as the libraries are separate i.e. dynamically linked.
2023-03-03 16:53:03 +0100 <pdw> I've seen that on some commercial tools.
2023-03-03 16:53:04 +0100mechap(~mechap@user/mechap) (Ping timeout: 248 seconds)
2023-03-03 16:53:10 +0100Sgeo(~Sgeo@user/sgeo)
2023-03-03 16:53:25 +0100 <geekosaur> yes, but the folks who care about this don't trust it
2023-03-03 16:53:57 +0100 <pdw> agree with the point, but there's not always an alternative, to be fair.
2023-03-03 16:54:49 +0100k8yun(~k8yun@user/k8yun) (Quit: Leaving)
2023-03-03 16:55:10 +0100mechap(~mechap@user/mechap)
2023-03-03 16:55:42 +0100 <pdw> I presume I'm right to believe the comment I read somewhere that said on Windows, Haskell outputs binaries with statically-linked libGMP?
2023-03-03 16:56:44 +0100califax(~califax@user/califx) (Ping timeout: 255 seconds)
2023-03-03 16:57:40 +0100 <pdw> (That's my main reason for investigating integer-simple: static linking wouldn't allow the dynamic linking clause to be applicable.)
2023-03-03 16:58:06 +0100 <mauke> LGPL does not require dynamic linking
2023-03-03 16:58:32 +0100mncheckm(~mncheck@193.224.205.254) (Remote host closed the connection)
2023-03-03 16:58:38 +0100kenran(~user@user/kenran) (Remote host closed the connection)
2023-03-03 16:59:13 +0100 <merijn> LGPL requires dynamic linking *OR* making all the required bits to relink statically available
2023-03-03 16:59:19 +0100 <pdw> mauke: that's interesting. How would that work?
2023-03-03 16:59:36 +0100use-value(~Thunderbi@2a00:23c6:8a03:2f01:9077:3e90:5614:a09f)
2023-03-03 16:59:53 +0100 <merijn> pdw: So you *can* distribute a statically linked binary IFF you also provide the application in a way that allows users to relink with a different library
2023-03-03 16:59:58 +0100mncheck(~mncheck@193.224.205.254)
2023-03-03 17:00:06 +0100 <mauke> provide object files for relinking
2023-03-03 17:00:25 +0100 <merijn> pdw: Note 4.D.0 here: https://www.gnu.org/licenses/lgpl-3.0.html
2023-03-03 17:01:02 +0100 <pdw> Yes, was looking at that, trying to fathom what "Minimal Corresponding Source" might mean. Sounded.... source-y.
2023-03-03 17:01:09 +0100mbuf(~Shakthi@49.204.138.106) (Quit: Leaving)
2023-03-03 17:01:10 +0100L29Ah(~L29Ah@wikipedia/L29Ah)
2023-03-03 17:01:36 +0100 <merijn> pdw: Basically provide *something* (possibly object files) that lets users link in a modified version of the LGPL lib
2023-03-03 17:02:13 +0100 <merijn> "The “Corresponding Application Code” for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work."
2023-03-03 17:02:14 +0100 <pdw> So if I'm doing a typical cabal build, I'd just ship all of the .o files from under dist-new? Something like that?
2023-03-03 17:02:26 +0100 <merijn> pdw: Fortunately, the LGPL defines those terms above ;)
2023-03-03 17:03:04 +0100 <pdw> Yes - Corresponding Application Code made sense (I think) in terms of the binary objects. Though it seems to suggest I also need to ship a linker.
2023-03-03 17:03:11 +0100 <merijn> pdw: If you can define a workflow that results in the user being able to link the things
2023-03-03 17:03:35 +0100Lycurgus(~juan@user/Lycurgus)
2023-03-03 17:03:40 +0100 <pdw> Can you shed any light on what Minimal Corresponding Source is talking about?
2023-03-03 17:03:53 +0100 <merijn> pdw: Are you dealing with proprietary code? Or something else?
2023-03-03 17:04:02 +0100 <pdw> I mean, I can parse the sentense, but can't see what it's talking about.
2023-03-03 17:04:32 +0100 <merijn> pdw: tbh, I *think* (but I'm not a lawyer) providing both a static and dynamic linked version of the program would *also* qualify as compliant
2023-03-03 17:04:35 +0100califax(~califax@user/califx)
2023-03-03 17:04:43 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2023-03-03 17:04:53 +0100 <pdw> This would be to distrubute code that'd be proprietary (commercial), so avoiding having to open up and/or distribute source would be the main issue.
2023-03-03 17:05:38 +0100 <mauke> minimal corresponding source is lgpl'd library source code
2023-03-03 17:05:48 +0100 <pdw> I've seen it done for some tools where the main application is a dynamically linked binary, and LGPL libraries/platforms/etc. are DLLs or shared objects shipped alongside.
2023-03-03 17:05:53 +0100 <mauke> which needs to stay open
2023-03-03 17:06:24 +0100 <pdw> ahh, well that makes lots of sense
2023-03-03 17:06:39 +0100freeside(~mengwong@103.252.202.85) (Ping timeout: 260 seconds)
2023-03-03 17:07:39 +0100 <pdw> so under LGPL 4.d.0) you'd ship the source for the correct library version (e.g. libGMP), plus the rest of the application in a standard binary format so that a user could re-link them.
2023-03-03 17:07:51 +0100 <merijn> pdw: Yes
2023-03-03 17:08:21 +0100 <merijn> Which is why I think a lot of the fear for libGMP is (mostly) unfounded
2023-03-03 17:08:39 +0100 <merijn> The most painful thing will be setting up a repeatable workflow for linking the final objects
2023-03-03 17:08:47 +0100 <merijn> But, that's a one time cost
2023-03-03 17:08:48 +0100 <pdw> agreed - that clause seems to be a very clear means for proprietary/LGPL code separation
2023-03-03 17:09:31 +0100 <merijn> Alternatively you could just provide static + dynamic versions and skip shipping the object code, but it's unclear to me whether that suffices
2023-03-03 17:10:08 +0100 <pdw> I think using a dynamic version would be covered under 4.d.1).
2023-03-03 17:10:35 +0100 <merijn> You can *probably* argue in court that it does, but probably want to avoid that. Could consider asking the copyright holder (i.e. FSF) for guidance on if they accept that
2023-03-03 17:10:36 +0100gentauro(~gentauro@user/gentauro) (Read error: Connection reset by peer)
2023-03-03 17:11:30 +0100 <pdw> maybe I'm missing something, but would a dynamically linked executable not be the obvious "suitable shared library mechanism for linking with the Library" ?
2023-03-03 17:11:34 +0100 <merijn> pdw: Well, it's clear that you can ship a dynamic version that's relinkable (under 4.d.1) and that you can ship a static version if you ship the rebuildable objects (4.d.0). It is unclear if the dynamic version absolves you from having to provide the relinkable objects when distributing the static version
2023-03-03 17:11:57 +0100 <pdw> ah, I see what you mean.
2023-03-03 17:12:21 +0100 <pdw> yes, I'd imagine it does given that (d) explicitly says "one of the following"
2023-03-03 17:12:35 +0100 <merijn> pdw: I *think* so too, but I'm not *sure*
2023-03-03 17:13:00 +0100 <pdw> :-) Yes, very fair point, especially with things such as this
2023-03-03 17:13:09 +0100 <merijn> But since the FSF is the copyright holder of GMP and only the copyright holder can sue, the easiest way to clarify is probably to just mail the GMP mailing lists and/or FSF and ask if that is sufficient
2023-03-03 17:13:14 +0100mei(~mei@user/mei) (Ping timeout: 268 seconds)
2023-03-03 17:13:23 +0100 <merijn> if you have an email reply that says "yes", that should be pretty conclusive in court
2023-03-03 17:13:30 +0100 <pdw> That is a very good suggestion
2023-03-03 17:14:15 +0100 <merijn> because it doesn't even matter for LGPL in general, all that matters is that the copyright holders of GMP agree with your interpretation :p
2023-03-03 17:14:21 +0100mncheck(~mncheck@193.224.205.254) (Ping timeout: 256 seconds)
2023-03-03 17:14:25 +0100 <merijn> (and maybe a paper trail of their agreeance)
2023-03-03 17:14:48 +0100 <pdw> precisely!
2023-03-03 17:15:23 +0100 <pdw> But I think the first thing for me will be to see whether I can produce a dynamically linked executable (i.e. not statically linking libGMP) at all
2023-03-03 17:15:26 +0100 <pdw> (on Windows)
2023-03-03 17:16:35 +0100gentauro(~gentauro@user/gentauro)
2023-03-03 17:16:41 +0100 <geekosaur> what you're all missing is (a) you're not corporate lawyers (b) the very fact that you need to sit down and try to figure it out is reason enough for said corporate lawyers to say "we don't want to have to deal with this"
2023-03-03 17:18:08 +0100freeside(~mengwong@103.252.202.85)
2023-03-03 17:20:38 +0100beteigeuze(~Thunderbi@a79-169-109-107.cpe.netcabo.pt) (Remote host closed the connection)
2023-03-03 17:20:39 +0100 <pdw> geekosaur: I certainly can't argue with that, and I imagine that people with access to a corporate legal department couldn't argue with it either...
2023-03-03 17:20:58 +0100beteigeuze(~Thunderbi@a79-169-109-107.cpe.netcabo.pt)
2023-03-03 17:20:59 +0100mei(~mei@user/mei)
2023-03-03 17:22:28 +0100segfaultfizzbuzz(~segfaultf@23-93-74-212.fiber.dynamic.sonic.net)
2023-03-03 17:22:36 +0100 <geekosaur> on a tangent, one of the things that came with gmp-bignum is that they can more easily try alternatives like libtommath now
2023-03-03 17:22:52 +0100 <geekosaur> tommath didn't work so well when they last tried it, but that was 15 years ago
2023-03-03 17:23:02 +0100mncheck(~mncheck@193.224.205.254)
2023-03-03 17:24:13 +0100 <merijn> pdw: I mean, Carmack managed to argue with multiple different ones in favour of GPLing Doom and other stuff :p
2023-03-03 17:24:22 +0100 <merijn> So it *can* be done :p
2023-03-03 17:26:04 +0100terrorjack(~terrorjac@2a01:4f8:1c1e:4e8c::)
2023-03-03 17:29:32 +0100ft(~ft@p3e9bc443.dip0.t-ipconnect.de)
2023-03-03 17:31:39 +0100ddellacosta(~ddellacos@146.70.166.10) (Quit: WeeChat 3.8)
2023-03-03 17:32:27 +0100Lycurgus(~juan@user/Lycurgus) (Quit: Exeunt: personae.ai-integration.biz)
2023-03-03 17:33:02 +0100ddellacosta(~ddellacos@146.70.166.10)
2023-03-03 17:33:40 +0100eggplantade(~Eggplanta@2600:1700:38c5:d800:e1f4:8ede:df26:d4a0)
2023-03-03 17:42:13 +0100dsrt^(~dsrt@c-24-30-76-89.hsd1.ga.comcast.net) (Ping timeout: 268 seconds)
2023-03-03 17:48:36 +0100 <pdw> merijn: Did you really just say "Hey, if Carmack can do it...?" in response to a question about what *my* options might be. :-D
2023-03-03 17:49:12 +0100 <pdw> That's definitely just made my afternoon
2023-03-03 17:49:27 +0100 <merijn> I'm just saying "sufficiently stubborn people can get legal to do what they want"
2023-03-03 17:51:18 +0100 <maerwald> can't see any stubborn people here
2023-03-03 17:53:43 +0100 <pdw> looks like there's an easy way out, in any case - I'd been looking at older GHC releases, but the newer ones appear to be available in integer-simple variants
2023-03-03 17:54:26 +0100 <pdw> (on Windows, at least)
2023-03-03 17:56:21 +0100 <pdw> might try building from source on Linux anyway, since the non-Alpine binary releases on Linux are all libGMP
2023-03-03 17:56:36 +0100Guest7149(~Guest71@31.56.132.77.rev.sfr.net)
2023-03-03 17:56:52 +0100Guest7149co_fi6
2023-03-03 17:57:14 +0100 <pdw> Is this a typo? https://www.haskell.org/ghc/download_ghc_9_4_4.html says "*Alpine (GMP bignum implementation)* ... this links against the integer-simple big-integer backend and therefore does not require libgmp."
2023-03-03 17:58:35 +0100tzh(~tzh@c-24-21-73-154.hsd1.or.comcast.net)
2023-03-03 17:59:18 +0100dekster(~dekster@2603-7000-1203-4d7c-8c00-75d6-3287-dba1.res6.spectrum.com) (Quit: ZZZzzz…)
2023-03-03 18:01:02 +0100razetime(~Thunderbi@117.193.1.135)
2023-03-03 18:01:44 +0100 <geekosaur> sounds like a copy-pasta
2023-03-03 18:01:46 +0100hammdist(~hammdist@67.169.114.135)
2023-03-03 18:01:53 +0100 <maerwald> alpine is a mess
2023-03-03 18:02:02 +0100 <geekosaur> from the prior entry
2023-03-03 18:02:03 +0100 <maerwald> some bindists are dynamic, some static, some gmp, some not
2023-03-03 18:02:23 +0100 <hammdist> hello. I want to use the ghc library to get an AST of a haskell program complete with type information. is this possible?
2023-03-03 18:02:55 +0100dhil(~dhil@80.208.56.181.static.fibianet.dk)
2023-03-03 18:05:32 +0100 <pdw> hammdist: I think I did something like this a while ago, to help me understand how Haskell expressions were being parsed. Not sure if it'll be what you need, but I'll see if I can dig it out
2023-03-03 18:06:14 +0100 <geekosaur> it should be possible but you need to make sure you run the typechecking phase, not just the parser or renamer
2023-03-03 18:06:51 +0100dekster(~dekster@2603-7000-1203-4d7c-8c00-75d6-3287-dba1.res6.spectrum.com)
2023-03-03 18:09:02 +0100 <hammdist> pdw: ah thanks if you have any code at all along these lines that would be most helpful
2023-03-03 18:11:13 +0100razetime(~Thunderbi@117.193.1.135) (Remote host closed the connection)
2023-03-03 18:13:54 +0100krei-se(~quassel@p5087440b.dip0.t-ipconnect.de)
2023-03-03 18:13:58 +0100co_fi6(~Guest71@31.56.132.77.rev.sfr.net) (Quit: Client closed)
2023-03-03 18:14:17 +0100use-value(~Thunderbi@2a00:23c6:8a03:2f01:9077:3e90:5614:a09f) (Quit: use-value)
2023-03-03 18:14:19 +0100machinedgod(~machinedg@d198-53-218-113.abhsia.telus.net) (Ping timeout: 248 seconds)
2023-03-03 18:16:00 +0100cheater_(~Username@user/cheater)
2023-03-03 18:17:03 +0100MajorBiscuit(~MajorBisc@c-001-018-056.client.tudelft.eduvpn.nl) (Quit: WeeChat 3.6)
2023-03-03 18:19:00 +0100cheater(~Username@user/cheater) (Ping timeout: 255 seconds)
2023-03-03 18:19:05 +0100cheater_cheater
2023-03-03 18:20:58 +0100gnalzo(~gnalzo@2a01:e0a:498:fd50:fcc6:bb5d:489a:ce8c)
2023-03-03 18:21:33 +0100 <zzz> i need help. i'm making an interactive gloss animationa and want to add sound to it. the sound (mostly basic waveforms interacting) should depend on the State i pass to gloss. i've been reading documentation and exploring some audio libraries but have no idea how to make this work. i have never done anything similar, so zero experience with audio libraries
2023-03-03 18:22:25 +0100 <pdw> is there a preferred pastebin service we like using in here? don't have a preference myself yet
2023-03-03 18:23:19 +0100 <zzz> pdw: see /topic
2023-03-03 18:26:50 +0100 <pdw> zzz: thanks, missed that
2023-03-03 18:27:58 +0100geekosaurwonders if that'll end up under haskell.org like play. did
2023-03-03 18:30:22 +0100 <pdw> hammdist: Have dug out a couple of things that I found useful. This was a couple of years ago, so there might be better options out there now.
2023-03-03 18:31:25 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-03-03 18:31:26 +0100 <pdw> There's Language.Haskell.Exts.Parser.parseExp (in package haskell-src-exts), which gives a very detailed breakdown of the AST resulting from parsing a Haskell expression.
2023-03-03 18:32:07 +0100 <pdw> That was a bit overkill for my needs, so I also found Language.Haskell.Meta.Parse.parseExp (package haskell-src-meta) which gives a more concise output.
2023-03-03 18:32:38 +0100 <pdw> I've put a short demonstration of them over here: https://paste.tomsmeding.com/SVfziuQ3
2023-03-03 18:32:45 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Remote host closed the connection)
2023-03-03 18:33:47 +0100 <pdw> I can't comment (per geekosaur's comment) as to whether those deal with the typechecking/renaming phases well enough for your situation, but they were of use to me.
2023-03-03 18:33:56 +0100jpds(~jpds@gateway/tor-sasl/jpds) (Ping timeout: 255 seconds)
2023-03-03 18:35:05 +0100jpds(~jpds@gateway/tor-sasl/jpds)
2023-03-03 18:36:40 +0100Guest711(~Guest71@46.56.132.77.rev.sfr.net)
2023-03-03 18:36:47 +0100Guest711(~Guest71@46.56.132.77.rev.sfr.net) (Client Quit)
2023-03-03 18:37:45 +0100zeenk(~zeenk@2a02:2f04:a20d:f900::7fe) (Quit: Konversation terminated!)
2023-03-03 18:37:51 +0100meiGuest6620
2023-03-03 18:37:57 +0100mei(~mei@user/mei)
2023-03-03 18:39:23 +0100Guest6620(~mei@user/mei) (Ping timeout: 248 seconds)
2023-03-03 18:39:44 +0100 <monochrom> Oh! I'll update the /topic for the new playground URL
2023-03-03 18:39:53 +0100ChanServ+o monochrom
2023-03-03 18:40:31 +0100 https://www.reddit.com/r/haskell | Admin: #haskell-ops | Offtopic: #haskell-offtopic | https://downloads.haskell.org https://play.haskell.org/ | Paste code/errors: https://paste.tomsmeding.com | Logs: https://ircbrowse.tomsmeding.com/browse/lchaskell
2023-03-03 18:40:57 +0100monochrom-o monochrom
2023-03-03 18:44:06 +0100 <int-e> monochrom: can you also insert a | in front of the playground link, please?
2023-03-03 18:44:18 +0100dcoutts_(~duncan@cpc69403-oxfd27-2-0-cust285.4-3.cable.virginm.net) (Ping timeout: 255 seconds)
2023-03-03 18:44:22 +0100 <monochrom> OK
2023-03-03 18:44:25 +0100ChanServ+o monochrom
2023-03-03 18:44:35 +0100 https://www.reddit.com/r/haskell | Admin: #haskell-ops | Offtopic: #haskell-offtopic | https://downloads.haskell.org | https://play.haskell.org/ | Paste code/errors: https://paste.tomsmeding.com | Logs: https://ircbrowse.tomsmeding.com/browse/lchaskell
2023-03-03 18:44:39 +0100 <int-e> thanks :)
2023-03-03 18:44:40 +0100monochrom-o monochrom
2023-03-03 18:44:47 +0100eggplantade(~Eggplanta@2600:1700:38c5:d800:e1f4:8ede:df26:d4a0) (Remote host closed the connection)
2023-03-03 18:45:12 +0100vpan(~0@212.117.1.172) (Quit: Leaving.)
2023-03-03 18:45:51 +0100cheater(~Username@user/cheater) (Read error: Connection reset by peer)
2023-03-03 18:46:14 +0100polyphem_(~rod@2a02:810d:840:8754:a35e:d131:c7e2:7e89)
2023-03-03 18:46:37 +0100cheater(~Username@user/cheater)
2023-03-03 18:48:46 +0100dcoutts_(~duncan@cpc69403-oxfd27-2-0-cust285.4-3.cable.virginm.net)
2023-03-03 18:52:36 +0100coot(~coot@2a02:a310:e241:1b00:ec1a:e9df:79ac:66ba) (Quit: coot)
2023-03-03 18:53:01 +0100coot(~coot@2a02:a310:e241:1b00:ec1a:e9df:79ac:66ba)
2023-03-03 18:53:39 +0100waleee(~waleee@2001:9b0:21c:4000:5bf9:6515:c030:57b7)
2023-03-03 18:55:00 +0100Nolrai(~Nolrai@c-73-240-99-98.hsd1.or.comcast.net)
2023-03-03 18:55:35 +0100Tuplanolla(~Tuplanoll@91-159-68-152.elisa-laajakaista.fi)
2023-03-03 18:57:47 +0100jpds(~jpds@gateway/tor-sasl/jpds) (Ping timeout: 255 seconds)
2023-03-03 18:59:48 +0100jpds(~jpds@gateway/tor-sasl/jpds)
2023-03-03 18:59:53 +0100econo(uid147250@user/econo)
2023-03-03 19:00:09 +0100nurupo(~nurupo.ga@user/nurupo) (Quit: nurupo.ga)
2023-03-03 19:00:24 +0100nurupo(~nurupo.ga@user/nurupo)
2023-03-03 19:00:49 +0100coot(~coot@2a02:a310:e241:1b00:ec1a:e9df:79ac:66ba) (Quit: coot)
2023-03-03 19:01:36 +0100npmania(~Thunderbi@91.193.7.62)
2023-03-03 19:03:13 +0100eggplantade(~Eggplanta@2600:1700:38c5:d800:e1f4:8ede:df26:d4a0)
2023-03-03 19:05:31 +0100segfaultfizzbuzz(~segfaultf@23-93-74-212.fiber.dynamic.sonic.net) (Ping timeout: 248 seconds)
2023-03-03 19:06:42 +0100 <hammdist> pdw: well thanks but I don't see much type information there. I will probably have to hack something together with invoking ghc lib as per geekosaur's comment
2023-03-03 19:08:33 +0100kuribas(~user@ptr-17d51engq5fqfsjpte2.18120a2.ip6.access.telenet.be) (Remote host closed the connection)
2023-03-03 19:08:54 +0100jakalx(~jakalx@base.jakalx.net) (Error from remote client)
2023-03-03 19:12:46 +0100npm_i_kurbus(~npm_i_kur@user/kurbus)
2023-03-03 19:13:14 +0100harveypwca(~harveypwc@2601:246:c180:a570:3828:d8:e523:3f67)
2023-03-03 19:17:19 +0100 <hammdist> https://paste.ee/p/r2h2W when I try to run the example code for ghc lib from https://wiki.haskell.org/GHC/As_a_library
2023-03-03 19:17:23 +0100geekosaur(~geekosaur@xmonad/geekosaur) (Quit: Leaving)
2023-03-03 19:17:58 +0100 <hammdist> (well it's not strictly speaking the example code I modified it a bit. but mainly asking how to resolve those imports)
2023-03-03 19:19:17 +0100werneta(~werneta@137.79.193.28)
2023-03-03 19:19:32 +0100geekosaur(~geekosaur@xmonad/geekosaur)
2023-03-03 19:20:04 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2023-03-03 19:21:07 +0100werneta(~werneta@137.79.193.28) (Client Quit)
2023-03-03 19:22:03 +0100beteigeuze(~Thunderbi@a79-169-109-107.cpe.netcabo.pt) (Ping timeout: 248 seconds)
2023-03-03 19:22:21 +0100mei(~mei@user/mei) (Remote host closed the connection)
2023-03-03 19:22:22 +0100 <hammdist> found that import statement. new error: https://paste.ee/p/A8O5y
2023-03-03 19:23:20 +0100teo(~teo@user/teo) (Ping timeout: 268 seconds)
2023-03-03 19:23:45 +0100dcoutts_(~duncan@cpc69403-oxfd27-2-0-cust285.4-3.cable.virginm.net) (Ping timeout: 260 seconds)
2023-03-03 19:25:29 +0100 <hammdist> signature of that function does not explain the error: `guessTarget :: GhcMonad m => String -> Maybe Phase -> m Target`
2023-03-03 19:26:01 +0100ChanServ+o litharge
2023-03-03 19:26:01 +0100litharge-bo *!*@static.167.190.119.168.clients.your-server.de$##fix_your_connection litharge
2023-03-03 19:26:15 +0100 <geekosaur> I think you'll need to ask in #ghc (and update the wiki accordingly; the ghc api is not very stable)
2023-03-03 19:28:08 +0100 <hammdist> ah I can see a different signature for my current version which is 9.4.4
2023-03-03 19:32:51 +0100beteigeuze(~Thunderbi@a79-169-109-107.cpe.netcabo.pt)
2023-03-03 19:37:09 +0100beteigeuze(~Thunderbi@a79-169-109-107.cpe.netcabo.pt) (Ping timeout: 256 seconds)
2023-03-03 19:37:37 +0100segfaultfizzbuzz(~segfaultf@23-93-74-212.fiber.dynamic.sonic.net)
2023-03-03 19:37:46 +0100ubert(~Thunderbi@2a02:8109:abc0:6434:a35b:2d28:c16d:4824) (Remote host closed the connection)
2023-03-03 19:37:46 +0100ububert
2023-03-03 19:37:51 +0100CiaoSen(~Jura@p200300c9570e91002a3a4dfffe84dbd5.dip0.t-ipconnect.de) (Ping timeout: 260 seconds)
2023-03-03 19:38:38 +0100cheater_(~Username@user/cheater)
2023-03-03 19:39:47 +0100kupi(uid212005@id-212005.hampstead.irccloud.com) (Quit: Connection closed for inactivity)
2023-03-03 19:39:48 +0100dsrt^(~dsrt@c-24-30-76-89.hsd1.ga.comcast.net)
2023-03-03 19:40:28 +0100 <pdw> hammdist: Sorry that wasn't much use - suspect this is a bit above my experience level. The only other thing I've seen is the 'Core' output from play.haskell.org, but I imagine that's related to what you're already looking into.
2023-03-03 19:41:15 +0100cheater(~Username@user/cheater) (Ping timeout: 260 seconds)
2023-03-03 19:41:24 +0100cheater_cheater
2023-03-03 19:41:25 +0100 <Nolrai> So if I have an iso that's partial one way is that a prism? No..thats not quite right.
2023-03-03 19:42:07 +0100segfaultfizzbuzz(~segfaultf@23-93-74-212.fiber.dynamic.sonic.net) (Ping timeout: 248 seconds)
2023-03-03 19:43:04 +0100merijn(~merijn@86-86-29-250.fixed.kpn.net) (Ping timeout: 268 seconds)
2023-03-03 19:43:31 +0100Lycurgus(~juan@user/Lycurgus)
2023-03-03 19:46:00 +0100 <c_wraith> Nolrai: no, that's correct
2023-03-03 19:46:22 +0100 <c_wraith> if it's total in one direction and partial in the other, it's a prism
2023-03-03 19:48:27 +0100beteigeuze(~Thunderbi@bl14-81-220.dsl.telepac.pt)
2023-03-03 19:52:47 +0100Luj(~Luj@2a01:e0a:5f9:9681:5880:c9ff:fe9f:3dfb) (Quit: The Lounge - https://thelounge.chat)
2023-03-03 19:53:09 +0100beteigeuze(~Thunderbi@bl14-81-220.dsl.telepac.pt) (Ping timeout: 255 seconds)
2023-03-03 19:55:03 +0100jmdaemon(~jmdaemon@user/jmdaemon)
2023-03-03 19:56:36 +0100segfaultfizzbuzz(~segfaultf@23-93-74-212.fiber.dynamic.sonic.net)
2023-03-03 19:58:48 +0100 <Nolrai> Yes, though in my particular case it was really more an lens in the oposite direction.
2023-03-03 20:01:58 +0100Lycurgus(~juan@user/Lycurgus) (Quit: Exeunt: personae.ai-integration.biz)
2023-03-03 20:04:21 +0100Kuttenbrunzer(~Kuttenbru@2a02:8108:8b80:1d48::a47c)
2023-03-03 20:09:34 +0100merijn(~merijn@86-86-29-250.fixed.kpn.net)
2023-03-03 20:18:06 +0100 <Jade[m]1> why is there no way for overloaded functions? They would work just fine if you simply required the first (only) parameter to be different in its type, right?
2023-03-03 20:18:47 +0100 <mauke> like methods?
2023-03-03 20:19:14 +0100 <geekosaur> type directed name resolution poses problems with type inference
2023-03-03 20:19:15 +0100segfaultfizzbuzz(~segfaultf@23-93-74-212.fiber.dynamic.sonic.net) (Ping timeout: 255 seconds)
2023-03-03 20:19:32 +0100 <Jade[m]1> Right now the only way to overload is via a class
2023-03-03 20:19:40 +0100 <Jade[m]1> geekosaur: ah, mh ok
2023-03-03 20:19:48 +0100 <geekosaur> as it is, typeclasses with more than one parameter need help for type inference to work (fundeps or associated types)
2023-03-03 20:20:48 +0100 <mauke> I import 4 'foo' functions from different modules. their first parameters have the following types: [a], f Char, a, String
2023-03-03 20:20:55 +0100 <mauke> which one does foo "hello" call?
2023-03-03 20:21:18 +0100 <Jade[m]1> mhm yeah that's an issue
2023-03-03 20:21:40 +0100 <Nolrai> In practice though type classes are what haskell uses to do what other languages do with overloading. Even if Idris and such have different division of labor.
2023-03-03 20:22:02 +0100zer0bitz_(~zer0bitz@2001:2003:f443:d600:fc46:678f:19c6:5892) ()
2023-03-03 20:22:15 +0100 <mauke> also, regular overloading is boring
2023-03-03 20:22:28 +0100 <mauke> you get the same effect by just using different names
2023-03-03 20:22:29 +0100 <geekosaur> you can still hit that with typeclasses, but they're all overlapping and require you to mark them as such — and no promises are made even in that case, although ghc will try
2023-03-03 20:22:38 +0100 <mauke> you can't abstract over overloading
2023-03-03 20:23:30 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2023-03-03 20:24:59 +0100zer0bitz(~zer0bitz@2001:2003:f443:d600:f59d:2630:d861:aa7e)
2023-03-03 20:26:26 +0100Nolrai(~Nolrai@c-73-240-99-98.hsd1.or.comcast.net) (Quit: Client closed)
2023-03-03 20:30:13 +0100segfaultfizzbuzz(~segfaultf@23-93-74-212.fiber.dynamic.sonic.net)
2023-03-03 20:34:25 +0100npm_i_kurbus(~npm_i_kur@user/kurbus) (Quit: Client closed)
2023-03-03 20:36:55 +0100finsternis(~X@23.226.237.192)
2023-03-03 20:38:31 +0100ardell(~ardell@user/ardell)
2023-03-03 20:42:45 +0100 <Midjak> hello
2023-03-03 20:43:06 +0100ardell(~ardell@user/ardell) (Client Quit)
2023-03-03 20:43:23 +0100ardell(~ardell@user/ardell)
2023-03-03 20:43:59 +0100merijn(~merijn@86-86-29-250.fixed.kpn.net) (Ping timeout: 248 seconds)
2023-03-03 20:44:12 +0100 <Midjak> Is there something in haskell for manipulation of large set of data. (as pandas by instance)
2023-03-03 20:44:33 +0100notzmv(~zmv@user/notzmv)
2023-03-03 20:51:15 +0100polyphem_(~rod@2a02:810d:840:8754:a35e:d131:c7e2:7e89) (Ping timeout: 260 seconds)
2023-03-03 20:51:43 +0100polyphem_(~rod@2a02:810d:840:8754:224e:f6ff:fe5e:bc17)
2023-03-03 20:52:32 +0100jpds(~jpds@gateway/tor-sasl/jpds) (Ping timeout: 255 seconds)
2023-03-03 20:53:19 +0100jpds(~jpds@gateway/tor-sasl/jpds)
2023-03-03 20:53:51 +0100harveypwca(~harveypwc@2601:246:c180:a570:3828:d8:e523:3f67) (Quit: Leaving)
2023-03-03 20:55:35 +0100 <davean> Midjak: There are a lot of things. Sadly more a set of tools than a framework.
2023-03-03 20:58:51 +0100tomboy64(~tomboy64@user/tomboy64) (Ping timeout: 255 seconds)
2023-03-03 20:59:36 +0100 <[exa]> Midjak: for actually big data there's some Spark support (see https://github.com/tweag/sparkle ). For smaller data you're usually sufficiently good off with manually created data structures, say in Repa or other strict arrays.
2023-03-03 21:00:30 +0100 <[exa]> Midjak: the "dataframe middleware" isn't required as direly as in pythons and R's because the language actually can compile pretty efficient code and data structures on itself.
2023-03-03 21:01:09 +0100 <Midjak> Well the framework aspect in pandas is not what I prefer. what would you advise me to start with Haskell ? What I would like could be the possibily to compose functions on the dataset.
2023-03-03 21:02:00 +0100 <Midjak> [exa], oh ! ok...
2023-03-03 21:02:15 +0100 <[exa]> depends a lot on what "dataset" is here. There's the huge stream-processing framework (conduit and others) that is pretty good for chewing big data
2023-03-03 21:02:35 +0100 <[exa]> esp. if the stuff doesn't really fit in memory, streams are nice
2023-03-03 21:02:44 +0100 <[exa]> for arrays and matrices, there's repa
2023-03-03 21:03:15 +0100 <[exa]> the rest might really depend on the usecase
2023-03-03 21:03:20 +0100 <davean> Yah, I usualyl chew through my datasets with a machines network and just stream it through.
2023-03-03 21:03:33 +0100 <davean> maybe some lenses
2023-03-03 21:04:14 +0100 <Midjak> I think repas it's what I need.
2023-03-03 21:04:28 +0100segfaultfizzbuzz(~segfaultf@23-93-74-212.fiber.dynamic.sonic.net) (Ping timeout: 268 seconds)
2023-03-03 21:04:33 +0100 <davean> Yah if you're more arrayish than stream-ish
2023-03-03 21:05:18 +0100 <Midjak> I work mainly with buig CSV I must shape
2023-03-03 21:05:24 +0100 <Midjak> not stream
2023-03-03 21:05:31 +0100 <davean> https://hackage.haskell.org/package/cassava
2023-03-03 21:05:35 +0100 <davean> What do you mean by shape?
2023-03-03 21:05:43 +0100 <davean> Most of my data is in CSV
2023-03-03 21:05:56 +0100 <[exa]> there's CSV and CSV :D
2023-03-03 21:06:12 +0100 <Midjak> pivot, column renaming, etc...
2023-03-03 21:06:17 +0100 <[exa]> for "narrow" data like 1 measurement per CSV line, cassava and streamings are OK
2023-03-03 21:06:32 +0100 <[exa]> for "wide" data like putting a 1000x1000 matrix to a CSV, repa it is
2023-03-03 21:06:43 +0100 <davean> Midjak: Yah, I do pivots and renaming and such streaming.
2023-03-03 21:06:47 +0100 <[exa]> if you want column names, cassava approach should be better
2023-03-03 21:06:55 +0100 <Midjak> well the CSV i have now has 2,103,552 rows
2023-03-03 21:07:04 +0100 <davean> Yes? Thats EXACTLY why I stream
2023-03-03 21:07:05 +0100 <[exa]> how many cols?
2023-03-03 21:07:06 +0100 <Midjak> it's big no ?
2023-03-03 21:07:08 +0100 <[exa]> no
2023-03-03 21:07:09 +0100 <davean> I don't have to hold it in memory
2023-03-03 21:07:17 +0100 <Midjak> 13 columns
2023-03-03 21:07:26 +0100 <[exa]> that's in-memory op
2023-03-03 21:07:27 +0100 <davean> 2M rows is NOTHING
2023-03-03 21:07:38 +0100sammelweis(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10) (Read error: Connection reset by peer)
2023-03-03 21:07:39 +0100 <Midjak> yes I know. I am streamish guy too
2023-03-03 21:07:40 +0100 <[exa]> unless your rows have like, images. :D
2023-03-03 21:07:42 +0100 <davean> So small I wouldn't even think about how I do it
2023-03-03 21:07:47 +0100 <Midjak> but not my boss :-D
2023-03-03 21:08:35 +0100 <davean> pivot is SLIGHTLY work in CSV streaming, but thats why I use machines.
2023-03-03 21:08:47 +0100 <Midjak> well in Haskell maybe davean
2023-03-03 21:08:51 +0100 <davean> Midjak: ?
2023-03-03 21:09:08 +0100sammelweis(~quassel@2601:401:8200:2d4c:bd9:d04c:7f69:eb10)
2023-03-03 21:09:14 +0100 <Midjak> with python without pandas it's big
2023-03-03 21:09:18 +0100machinedgod(~machinedg@d198-53-218-113.abhsia.telus.net)
2023-03-03 21:09:25 +0100 <davean> interesting
2023-03-03 21:09:51 +0100 <[exa]> Midjak: if in-memory performance is a concern I'd tell you to try julia on that, it might be the most cost-effective solution by far
2023-03-03 21:09:56 +0100 <davean> Hum, maybe I should publish some of my CSV ops
2023-03-03 21:10:06 +0100 <Midjak> I didn't try, but just opening the file and create the df takes a while
2023-03-03 21:10:16 +0100 <[exa]> Midjak: pythons. :D
2023-03-03 21:10:33 +0100 <Midjak> yeah...
2023-03-03 21:10:36 +0100 <davean> Midjak: I'm REALLY busy today, but do you have some pseudo code of what you want to do as examples?
2023-03-03 21:11:09 +0100 <davean> (You certainly should move forward now, but it might make an interesting conversation and comparison in the future)
2023-03-03 21:12:59 +0100 <Midjak> I'm actually starting a new job on Monday and I'm looking at their stack (Pandas, Dash) and I was wondering how Haskell handles that kind of work. Now I'm just trying to manipulate the data and display it with Dash.
2023-03-03 21:13:41 +0100 <Midjak> Yes it will be a real pleasure to have feedback on this from Haskell world.
2023-03-03 21:13:49 +0100machinedgod(~machinedg@d198-53-218-113.abhsia.telus.net) (Remote host closed the connection)
2023-03-03 21:14:22 +0100 <Midjak> Julia attracts me for a while
2023-03-03 21:14:33 +0100 <[exa]> Midjak: haskell is for doing stuff as-right-as-practically-possible; if they do quick&dirty prototyping most of the time it might not be
2023-03-03 21:14:38 +0100 <[exa]> *very effective
2023-03-03 21:15:15 +0100 <Midjak> But I had to choose between what I want to learn. At now I am on Haskell and Rust (Python and JS at work)
2023-03-03 21:15:50 +0100 <[exa]> OTOH if you have a well-specified problem where you need the data processing to work perfectly forever, haskell.
2023-03-03 21:19:21 +0100masterbuilder(~masterbui@user/masterbuilder) (Quit: leaving)
2023-03-03 21:20:12 +0100machinedgod(~machinedg@d198-53-218-113.abhsia.telus.net)
2023-03-03 21:23:15 +0100 <Midjak> i have to go now but davean [exa] we can continue later on if you want
2023-03-03 21:23:19 +0100 <[exa]> sure :]
2023-03-03 21:27:43 +0100dcoutts_(~duncan@cpc69403-oxfd27-2-0-cust285.4-3.cable.virginm.net)
2023-03-03 21:29:28 +0100 <davean> [exa]: Honestly I find Haskell *with the right support libraries* great for throwing stuff together, its when you change domain you run into work.
2023-03-03 21:31:30 +0100 <monochrom> python users proved that with the right libraries you can throw stuff together and the language doesn't matter.
2023-03-03 21:32:17 +0100 <monochrom> Look at their machine learning users, algebra users, physics users.
2023-03-03 21:33:11 +0100 <monochrom> (SymPy for the algebra users for example)
2023-03-03 21:34:04 +0100dcoutts_(~duncan@cpc69403-oxfd27-2-0-cust285.4-3.cable.virginm.net) (Ping timeout: 268 seconds)
2023-03-03 21:34:59 +0100masterbuilder(~masterbui@user/masterbuilder)
2023-03-03 21:35:42 +0100[exa](~exa@srv3n.blesmrt.net) (Remote host closed the connection)
2023-03-03 21:38:24 +0100dsrt^(~dsrt@c-24-30-76-89.hsd1.ga.comcast.net) (Ping timeout: 248 seconds)
2023-03-03 21:39:03 +0100dekster(~dekster@2603-7000-1203-4d7c-8c00-75d6-3287-dba1.res6.spectrum.com) (Quit: ZZZzzz…)
2023-03-03 21:39:17 +0100dsrt^(~dsrt@c-24-30-76-89.hsd1.ga.comcast.net)
2023-03-03 21:39:30 +0100AmyMalik(ellenor@callbox.trd.is) (Quit: Bye Open Projects!)
2023-03-03 21:40:23 +0100dekster(~dekster@2603-7000-1203-4d7c-8c00-75d6-3287-dba1.res6.spectrum.com)
2023-03-03 21:41:44 +0100[exa](~exa@user/exa/x-3587197)
2023-03-03 21:45:39 +0100Ellenor(ellenor@callbox.trd.is)
2023-03-03 21:49:27 +0100segfaultfizzbuzz(~segfaultf@23-93-74-212.fiber.dynamic.sonic.net)
2023-03-03 21:49:36 +0100jmdaemon(~jmdaemon@user/jmdaemon) (Ping timeout: 248 seconds)
2023-03-03 21:51:27 +0100teo(~quassel@user/teo)
2023-03-03 21:51:36 +0100ardell(~ardell@user/ardell) (Quit: Konversation terminated!)
2023-03-03 21:54:56 +0100Sgeo(~Sgeo@user/sgeo) (Ping timeout: 248 seconds)
2023-03-03 21:58:19 +0100pavonia(~user@user/siracusa)
2023-03-03 21:58:36 +0100tcard(~tcard@2400:4051:5801:7500:cf17:befc:ff82:5303) (Read error: Connection reset by peer)
2023-03-03 22:00:43 +0100eggplantade(~Eggplanta@2600:1700:38c5:d800:e1f4:8ede:df26:d4a0) (Remote host closed the connection)
2023-03-03 22:00:56 +0100Sgeo(~Sgeo@user/sgeo)
2023-03-03 22:01:05 +0100wootehfoot(~wootehfoo@user/wootehfoot)
2023-03-03 22:01:33 +0100eggplantade(~Eggplanta@104-55-37-220.lightspeed.sntcca.sbcglobal.net)
2023-03-03 22:02:55 +0100tcard(~tcard@2400:4051:5801:7500:cf17:befc:ff82:5303)
2023-03-03 22:04:06 +0100ix(~ix@213.205.242.28) (Ping timeout: 255 seconds)
2023-03-03 22:11:05 +0100dcoutts_(~duncan@cpc69403-oxfd27-2-0-cust285.4-3.cable.virginm.net)
2023-03-03 22:12:41 +0100merijn(~merijn@86-86-29-250.fixed.kpn.net)
2023-03-03 22:12:59 +0100 <remexre> this is maybe a sign that i'm going overboard on DataKinds+TypeFamilies, but
2023-03-03 22:13:19 +0100 <remexre> I've got a type family that does a map over a type-level list (as in a DataKinds'd one)
2023-03-03 22:13:43 +0100 <remexre> is there any way I can get the typechecker to realize that (F xs ~ '[]) implies (xs ~ '[]) ?
2023-03-03 22:15:09 +0100 <geekosaur> I suspect you'd need a plugin that added the necessary evidence. ghc's not real smart about that kind of thing
2023-03-03 22:16:06 +0100 <geekosaur> yet another reason you should really consider Idris if you're doing heavy type level stuff…
2023-03-03 22:16:59 +0100 <geekosaur> (I'm not sure DH would help with this, since it's not a dependent type, just a major shortcoming in ghc's type level machinery)
2023-03-03 22:18:23 +0100 <remexre> I mean, in Idris I'd still need to prove this too, right?
2023-03-03 22:18:40 +0100 <remexre> well, I guess "map preserves structure" is almost certainly in the stdlib, but still
2023-03-03 22:19:40 +0100 <geekosaur> right. but you'd only have to prove it once. a ghc plugin would have to add the proof/evidence everywhere it was used
2023-03-03 22:21:06 +0100 <geekosaur> (see for example how natnormalise forces ghc to accept various "obvious" rules)
2023-03-03 22:22:15 +0100Kuttenbrunzer(~Kuttenbru@2a02:8108:8b80:1d48::a47c) (Quit: Where is it)
2023-03-03 22:28:29 +0100takuan_dozo(~takuan@178-116-218-225.access.telenet.be) (Remote host closed the connection)
2023-03-03 22:28:43 +0100jwiegley(~jwiegley@76-234-69-149.lightspeed.frokca.sbcglobal.net) (Ping timeout: 248 seconds)
2023-03-03 22:28:51 +0100jwiegley_(~jwiegley@76-234-69-149.lightspeed.frokca.sbcglobal.net)
2023-03-03 22:29:25 +0100johnw(~johnw@76-234-69-149.lightspeed.frokca.sbcglobal.net) (Ping timeout: 256 seconds)
2023-03-03 22:29:51 +0100johnw(~johnw@76-234-69-149.lightspeed.frokca.sbcglobal.net)
2023-03-03 22:31:41 +0100jmdaemon(~jmdaemon@user/jmdaemon)
2023-03-03 22:32:54 +0100gurkenglas(~gurkengla@dynamic-046-114-176-169.46.114.pool.telefonica.de) (Ping timeout: 255 seconds)
2023-03-03 22:33:11 +0100trev(~trev@user/trev) (Remote host closed the connection)
2023-03-03 22:37:34 +0100whatsupdoc(uid509081@id-509081.hampstead.irccloud.com)
2023-03-03 22:38:01 +0100teo(~quassel@user/teo) ()
2023-03-03 22:39:32 +0100gurkenglas(~gurkengla@dynamic-046-114-176-169.46.114.pool.telefonica.de)
2023-03-03 22:47:18 +0100merijn(~merijn@86-86-29-250.fixed.kpn.net) (Ping timeout: 255 seconds)
2023-03-03 22:52:22 +0100krei-se(~quassel@p5087440b.dip0.t-ipconnect.de) (Remote host closed the connection)
2023-03-03 22:58:14 +0100 <geekosaur> whee! [ANNOUNCE] GHC 9.6.1-rc1 is now available
2023-03-03 22:58:46 +0100 <Rembane> \o/
2023-03-03 23:00:00 +0100dekster(~dekster@2603-7000-1203-4d7c-8c00-75d6-3287-dba1.res6.spectrum.com) (Quit: ZZZzzz…)
2023-03-03 23:00:32 +0100dekster(~dekster@2603-7000-1203-4d7c-8c00-75d6-3287-dba1.res6.spectrum.com)
2023-03-03 23:01:19 +0100Midjak2(~Midjak@82.66.147.146)
2023-03-03 23:01:43 +0100Midjak(~Midjak@82.66.147.146) (Ping timeout: 256 seconds)
2023-03-03 23:01:59 +0100 <monochrom> ooohhh js and webasm
2023-03-03 23:02:00 +0100Midjak2(~Midjak@82.66.147.146) (Read error: Connection reset by peer)
2023-03-03 23:02:04 +0100 <tomsmeding> what's the difference between an alpha and a release candidate :p
2023-03-03 23:02:31 +0100 <monochrom> but "tech review" haha ok
2023-03-03 23:02:56 +0100 <monochrom> But delimited cont is the one everyone was waiting for heh
2023-03-03 23:03:49 +0100 <monochrom> Will the playground have this rc1 soon? :)
2023-03-03 23:04:26 +0100 <monochrom> I think alpha is less ready than beta, and rc is more ready than beta.
2023-03-03 23:04:39 +0100 <monochrom> or maybe rc=beta
2023-03-03 23:05:33 +0100 <darkling> rc should be post beta
2023-03-03 23:06:07 +0100 <monochrom> Somehow GHC doesn't have beta, just has alpha, rc, release
2023-03-03 23:06:28 +0100 <darkling> I guess every project has its own criteria.
2023-03-03 23:07:07 +0100ubert(~Thunderbi@p200300ecdf29471416a399119c633262.dip0.t-ipconnect.de) (Ping timeout: 248 seconds)
2023-03-03 23:07:08 +0100 <darkling> (I've never forgiven the maven developers for breaking maven by removing an API function between two RCs)
2023-03-03 23:07:09 +0100ub(~Thunderbi@p548c9fde.dip0.t-ipconnect.de)
2023-03-03 23:07:48 +0100 <monochrom> Yikes. But it may depend on why they did it.
2023-03-03 23:09:27 +0100ububert
2023-03-03 23:09:52 +0100 <tomsmeding> monochrom: when ghcup has it :)
2023-03-03 23:10:04 +0100 <monochrom> heh fair
2023-03-03 23:10:23 +0100 <geekosaur> that should be soonish
2023-03-03 23:11:28 +0100 <tomsmeding> ping me if you see it in ghcup and it's not on the playground yet (this is currently a manual process)
2023-03-03 23:11:58 +0100 <monochrom> Hrm, "type data" is not an entirely intuitive name.
2023-03-03 23:12:05 +0100cheater(~Username@user/cheater) (Read error: Connection reset by peer)
2023-03-03 23:12:49 +0100cheater(~Username@user/cheater)
2023-03-03 23:12:54 +0100 <monochrom> But I guess in the interest of minimizing reserved words...
2023-03-03 23:13:25 +0100akegalj(~akegalj@93-138-62-24.adsl.net.t-com.hr) (Quit: leaving)
2023-03-03 23:14:56 +0100 <tomsmeding> though any lowercase word after "type" or "data" would've been fine syntax-wise
2023-03-03 23:15:02 +0100 <tomsmeding> but maybe not very future-proof
2023-03-03 23:15:16 +0100gnalzo_(~gnalzo@2a01:e0a:498:fd50:fcc6:bb5d:489a:ce8c)
2023-03-03 23:15:29 +0100 <tomsmeding> oh, or would it? Perhaps 'data c a => T = MkT' is valid syntax with DatatypeContexts
2023-03-03 23:16:13 +0100 <geekosaur> I think "instance" already set how they deal
2023-03-03 23:16:28 +0100 <monochrom> But it means that c is not the name you are defining.
2023-03-03 23:16:49 +0100 <tomsmeding> hah yes 'data c a => T c a = MkT' is accepted with -XDatatypeContexts -XConstraintKinds
2023-03-03 23:16:57 +0100 <monochrom> Ah nevermind, you are making that point.
2023-03-03 23:16:59 +0100gnalzo(~gnalzo@2a01:e0a:498:fd50:fcc6:bb5d:489a:ce8c) (Ping timeout: 264 seconds)
2023-03-03 23:17:20 +0100 <tomsmeding> monochrom: yeah, that the word after "data" would really need to be a reserved word, not just any lowercase thing
2023-03-03 23:17:30 +0100dekster(~dekster@2603-7000-1203-4d7c-8c00-75d6-3287-dba1.res6.spectrum.com) (Quit: ZZZzzz…)
2023-03-03 23:17:42 +0100 <tomsmeding> perhaps it would still be unambiguous after "type", but then that's somewhat fragile
2023-03-03 23:18:27 +0100dekster(~dekster@2603-7000-1203-4d7c-8c00-75d6-3287-dba1.res6.spectrum.com)
2023-03-03 23:19:35 +0100Midjak(~Midjak@82.66.147.146)
2023-03-03 23:19:43 +0100dhil(~dhil@80.208.56.181.static.fibianet.dk) (Ping timeout: 248 seconds)
2023-03-03 23:20:32 +0100gnalzo_gnalzo
2023-03-03 23:24:21 +0100__monty__(~toonn@user/toonn) (Quit: leaving)
2023-03-03 23:24:48 +0100hammdist(~hammdist@67.169.114.135) (Quit: Client closed)
2023-03-03 23:27:10 +0100ix(~ix@46.68.8.176)
2023-03-03 23:30:37 +0100kritzefitz(~kritzefit@debian/kritzefitz) (Ping timeout: 268 seconds)
2023-03-03 23:32:40 +0100michalz(~michalz@185.246.204.121) (Remote host closed the connection)
2023-03-03 23:32:41 +0100dcoutts_(~duncan@cpc69403-oxfd27-2-0-cust285.4-3.cable.virginm.net) (Remote host closed the connection)
2023-03-03 23:33:03 +0100dcoutts_(~duncan@cpc69403-oxfd27-2-0-cust285.4-3.cable.virginm.net)
2023-03-03 23:33:20 +0100bgs(~bgs@212-85-160-171.dynamic.telemach.net) (Remote host closed the connection)
2023-03-03 23:33:40 +0100kritzefitz(~kritzefit@debian/kritzefitz)
2023-03-03 23:34:34 +0100gnalzo(~gnalzo@2a01:e0a:498:fd50:fcc6:bb5d:489a:ce8c) (Ping timeout: 252 seconds)
2023-03-03 23:35:07 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2023-03-03 23:38:23 +0100gmg(~user@user/gehmehgeh)
2023-03-03 23:39:41 +0100EllenorAmyMalik
2023-03-03 23:40:18 +0100merijn(~merijn@86-86-29-250.fixed.kpn.net)
2023-03-03 23:40:20 +0100segfaultfizzbuzz(~segfaultf@23-93-74-212.fiber.dynamic.sonic.net) (Ping timeout: 246 seconds)
2023-03-03 23:42:13 +0100gnalzo(~gnalzo@2a01:e0a:498:fd50:fcc6:bb5d:489a:ce8c)
2023-03-03 23:44:41 +0100pdw(~user@197.33.187.81.in-addr.arpa) (Quit: ERC (IRC client for Emacs 26.3))
2023-03-03 23:45:25 +0100merijn(~merijn@86-86-29-250.fixed.kpn.net) (Ping timeout: 268 seconds)
2023-03-03 23:47:26 +0100gnalzo(~gnalzo@2a01:e0a:498:fd50:fcc6:bb5d:489a:ce8c) (Quit: WeeChat 3.8)
2023-03-03 23:47:37 +0100deksterAlbina_Pavlovna
2023-03-03 23:57:50 +0100beteigeuze(~Thunderbi@bl14-81-220.dsl.telepac.pt)