2025/07/21

Newest at the top

2025-07-21 17:44:23 +0200cashew(~cashewsta@pool-71-169-14-231.pghkny.fios.verizon.net)
2025-07-21 17:43:47 +0200Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net)
2025-07-21 17:42:59 +0200Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Read error: Connection reset by peer)
2025-07-21 17:40:42 +0200gmg(~user@user/gehmehgeh) gehmehgeh
2025-07-21 17:40:16 +0200Lycurgus(~juan@user/Lycurgus) (Quit: irc.renjuan.org (juan@acm.org))
2025-07-21 17:38:06 +0200trickard_(~trickard@cpe-62-98-47-163.wireline.com.au)
2025-07-21 17:37:52 +0200trickard_(~trickard@cpe-62-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2025-07-21 17:33:07 +0200lortabac(~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4) (Quit: WeeChat 4.5.2)
2025-07-21 17:27:25 +0200Square2(~Square@user/square) Square
2025-07-21 17:27:16 +0200Lycurgus(~juan@user/Lycurgus) Lycurgus
2025-07-21 17:26:52 +0200Lycurgus(~juan@user/Lycurgus) (Client Quit)
2025-07-21 17:26:52 +0200WorldControl(~juan@121.sub-75-246-203.myvzw.com) (Client Quit)
2025-07-21 17:26:27 +0200WorldControl(~juan@121.sub-75-246-203.myvzw.com)
2025-07-21 17:25:40 +0200Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net)
2025-07-21 17:25:13 +0200tromp(~textual@2001:1c00:3487:1b00:e568:6986:f662:22ea)
2025-07-21 17:24:52 +0200simplystuart(~simplystu@c-75-75-152-164.hsd1.pa.comcast.net)
2025-07-21 17:24:37 +0200Lycurgus(~juan@user/Lycurgus) Lycurgus
2025-07-21 17:24:18 +0200simplystuart(~simplystu@c-75-75-152-164.hsd1.pa.comcast.net) (Ping timeout: 252 seconds)
2025-07-21 17:23:19 +0200 <int-e> EvanR: I see you're embracing pure laziness.
2025-07-21 17:20:20 +0200Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Read error: Connection reset by peer)
2025-07-21 17:18:40 +0200SlackCoder(~SlackCode@remote.nationalgallery.org.ky) SlackCoder
2025-07-21 17:18:04 +0200merijn(~merijn@77.242.116.146) merijn
2025-07-21 17:15:51 +0200 <EvanR> that code wasn't meant to be executed. The AST for that code we never meant to be compiled. The string containing the raw code characters was never meant to be parsed
2025-07-21 17:05:58 +0200merijn(~merijn@77.242.116.146) (Ping timeout: 240 seconds)
2025-07-21 17:04:37 +0200 <sprout> code was never meant to be executed anyway
2025-07-21 17:04:23 +0200 <EvanR> there are 4 lights
2025-07-21 17:04:13 +0200 <int-e> sprout: with great power comes great responsibility
2025-07-21 17:03:42 +0200 <lambdabot> 5
2025-07-21 17:03:41 +0200 <sprout> > let 2 + 2 = 5 in 2 + 2
2025-07-21 17:02:07 +0200 <int-e> (it's not without downsides; most notable, it doesn't work well together with `where`)
2025-07-21 17:01:53 +0200EvanR(~EvanR@user/evanr) EvanR
2025-07-21 17:00:11 +0200ttybitnik(~ttybitnik@user/wolper) (Remote host closed the connection)
2025-07-21 16:59:26 +0200 <int-e> the problem with just disallowing shadowing is that it doesn't prevent you from using the old value
2025-07-21 16:59:08 +0200 <int-e> this is why I actually use the foo x | x <- x+1 = x style (in moderation)
2025-07-21 16:57:43 +0200 <merijn> Shadowing is just never worth it
2025-07-21 16:57:36 +0200 <merijn> int-e: This is why I started using shadow warnings everywhere
2025-07-21 16:54:52 +0200EvanR(~EvanR@user/evanr) (Quit: Leaving)
2025-07-21 16:51:07 +0200gmg(~user@user/gehmehgeh) (Quit: Leaving)
2025-07-21 16:51:01 +0200r-sta(~r-sta@cpc142694-benw13-2-0-cust901.16-2.cable.virginm.net) (Quit: Client closed)
2025-07-21 16:50:59 +0200 <r-sta> thanks for the tips. i might return for tips on stack tracing
2025-07-21 16:50:39 +0200 <r-sta> im gona take a break before my computer loops itself down the stairs
2025-07-21 16:50:22 +0200 <r-sta> because my GP didnt!
2025-07-21 16:50:13 +0200 <r-sta> (anyone know the difference between an sNRI and an SNRI ?)
2025-07-21 16:50:04 +0200 <EvanR> colliding or shadowing variables names defeats one of the best ways the compiler can tell you about your nonsense code: variable name goes nowhere or has wrong type
2025-07-21 16:49:43 +0200 <r-sta> EvarR: thats actually quite interesting
2025-07-21 16:49:06 +0200 <r-sta> i think i might just throw my computer out the window, move to a new country, learn meditation techniques, invent some paradoxical SSRIs and start afresh
2025-07-21 16:49:02 +0200 <EvanR> though that doesn't help with <<loop>>
2025-07-21 16:48:50 +0200 <EvanR> this is why haskell is pure, because they predicted that debugging a combination of lazy and effectful would be insane
2025-07-21 16:48:49 +0200 <int-e> My favorite <<loop>> was somewhere on haskell-cafe ages ago where somebody had code that used r,s,t as variables, and r,g,b as color values... and failed to spot the overlap :-)
2025-07-21 16:48:27 +0200 <r-sta> at least now i *know* there was non-determinism