2024/11/06

Newest at the top

2024-11-06 22:19:36 +0100takuan(~takuan@178-116-218-225.access.telenet.be) (Remote host closed the connection)
2024-11-06 22:18:07 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 264 seconds)
2024-11-06 22:14:09 +0100wootehfoot(~wootehfoo@user/wootehfoot) (Quit: Leaving)
2024-11-06 22:13:01 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-11-06 22:02:25 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds)
2024-11-06 22:02:00 +0100Everything(~Everythin@46.211.117.180) Everything
2024-11-06 21:57:38 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-11-06 21:56:54 +0100machinedgod(~machinedg@d108-173-18-100.abhsia.telus.net) (Ping timeout: 252 seconds)
2024-11-06 21:55:19 +0100ephilalethes(~noumenon@113.51-175-156.customer.lyse.net) noumenon
2024-11-06 21:50:34 +0100peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 260 seconds)
2024-11-06 21:46:38 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds)
2024-11-06 21:42:17 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-11-06 21:31:46 +0100alphazone(~alphazone@2.219.56.221) (Ping timeout: 272 seconds)
2024-11-06 21:31:09 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 260 seconds)
2024-11-06 21:29:58 +0100alphazone_(~alphazone@2.219.56.221)
2024-11-06 21:24:11 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-11-06 21:21:20 +0100Square2(~Square4@user/square) (Ping timeout: 252 seconds)
2024-11-06 21:18:56 +0100briandaed(~root@185.234.210.211.r.toneticgroup.pl) (Remote host closed the connection)
2024-11-06 21:17:50 +0100ubert(~Thunderbi@77.119.163.56.wireless.dyn.drei.com) (Ping timeout: 255 seconds)
2024-11-06 21:17:26 +0100Square(~Square@user/square) Square
2024-11-06 21:12:19 +0100 <haskellbridge> <sm> PSA: Unlike most haskell services, hoogle.haskell.org is slower outside the US (eg 1s response time in Europe instead of 1/4s). If you'd like to make it faster, improve its rudimentary web app, eg to provide good caching headers !
2024-11-06 21:11:43 +0100 <dolio> Panic sounds like a synonym for error. I know what that is.
2024-11-06 21:10:43 +0100ash3en(~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Quit: ash3en)
2024-11-06 21:04:49 +0100 <EvanR> probably
2024-11-06 21:04:42 +0100 <monochrom> Well OK I guess I should be cynical about humanity again.
2024-11-06 21:04:20 +0100 <monochrom> Oh haha.
2024-11-06 21:04:08 +0100 <EvanR> more like "how do I catch a panic so I can do slick control flow fu"
2024-11-06 21:02:33 +0100 <monochrom> It is a good thing that beginners ask "I don't get 'panic', what is it for?" instead of the Dunning-Kruger effect of deluding themselves into believing that they understand.
2024-11-06 21:00:42 +0100caconym(~caconym@user/caconym) caconym
2024-11-06 21:00:04 +0100caconym(~caconym@user/caconym) (Quit: bye)
2024-11-06 20:59:59 +0100 <monochrom> That is still much better than "I know what 'error' means, don't educate me".
2024-11-06 20:58:42 +0100 <EvanR> there's still plenty of stack overflow going over the intention of panic and how it won't work for "exceptions as control flow" common in other languages
2024-11-06 20:54:04 +0100 <monochrom> Beginners don't know community consensus. What beginners do is look at meaningful names and believe that they are actually honest. We had the misstep of calling it "error" so beginners think it just means the same "error" from languages they already know. Rust has the wisdom to call it "panic".
2024-11-06 20:53:25 +0100weary-traveler(~user@user/user363627) (Remote host closed the connection)
2024-11-06 20:53:00 +0100smiesner(b0cf5acf8c@user/smiesner) smiesner
2024-11-06 20:52:54 +0100peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich
2024-11-06 20:52:53 +0100smiesner(b0cf5acf8c@user/smiesner) (Ping timeout: 245 seconds)
2024-11-06 20:52:49 +0100ljdarj1(~Thunderbi@user/ljdarj) (Ping timeout: 265 seconds)
2024-11-06 20:52:24 +0100ft(~ft@p4fc2a216.dip0.t-ipconnect.de) ft
2024-11-06 20:51:26 +0100ljdarj(~Thunderbi@user/ljdarj) ljdarj
2024-11-06 20:51:07 +0100ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 264 seconds)
2024-11-06 20:50:20 +0100ft(~ft@p4fc2a216.dip0.t-ipconnect.de) (Quit: Lost terminal)
2024-11-06 20:49:50 +0100 <EvanR> or put them in Chans
2024-11-06 20:49:38 +0100 <EvanR> you can also put bottoms in MVars and screw over whoever has access to it
2024-11-06 20:48:11 +0100ljdarj1(~Thunderbi@user/ljdarj) ljdarj
2024-11-06 20:46:03 +0100 <EvanR> did not think of that level of broken code
2024-11-06 20:45:42 +0100 <EvanR> throwing an exception which is a bottom sounds ridiculous
2024-11-06 20:44:50 +0100 <EvanR> I'm mainly talking about async (the library)
2024-11-06 20:44:38 +0100 <EvanR> if the thread crashes no
2024-11-06 20:44:31 +0100 <EvanR> if forkIO itself crashes sure