2024/09/20

Newest at the top

2024-09-20 15:33:12 +0200 <tomsmeding> (for (>=>) that depends on the monad instance)
2024-09-20 15:33:07 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Ping timeout: 264 seconds)
2024-09-20 15:33:02 +0200 <tomsmeding> hence, at least for (.), GHC will be able to beta-reduce the (.) chain very easily
2024-09-20 15:32:33 +0200 <tomsmeding> the fixity of (.) and (>=>) only influences the nesting order of manually written chains of (.) or (>=>), which are by construction bounded length (your source file is not infinitely long) and GHC can see all of them together
2024-09-20 15:31:48 +0200youthlic(~Thunderbi@user/youthlic)
2024-09-20 15:31:36 +0200 <tomsmeding> in practice it's more like `a >>= \x -> b >>= \y -> c`, which is associated perfectly well
2024-09-20 15:31:21 +0200 <tomsmeding> `a >>= b >>= c` is exceedingly rare
2024-09-20 15:30:59 +0200 <tomsmeding> Inst: _does_ (>>=) leak?
2024-09-20 15:29:43 +0200athan(~athan@syn-098-153-145-140.biz.spectrum.com) (Quit: Konversation terminated!)
2024-09-20 15:28:30 +0200srazkvt(~sarah@user/srazkvt) (Read error: Connection reset by peer)
2024-09-20 15:28:20 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net)
2024-09-20 15:28:10 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 272 seconds)
2024-09-20 15:20:48 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl)
2024-09-20 15:14:14 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 272 seconds)
2024-09-20 15:09:07 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl)
2024-09-20 15:00:32 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Ping timeout: 252 seconds)
2024-09-20 15:00:21 +0200 <kuribas> Inst: which instance?
2024-09-20 14:58:19 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds)
2024-09-20 14:56:05 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net)
2024-09-20 14:53:09 +0200rvalue(~rvalue@user/rvalue)
2024-09-20 14:52:48 +0200rvalue(~rvalue@user/rvalue) (Remote host closed the connection)
2024-09-20 14:49:36 +0200ft(~ft@p508db65d.dip0.t-ipconnect.de)
2024-09-20 14:47:15 +0200srazkvt(~sarah@user/srazkvt)
2024-09-20 14:41:21 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Ping timeout: 248 seconds)
2024-09-20 14:37:01 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl)
2024-09-20 14:35:11 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net)
2024-09-20 14:20:11 +0200xff0x(~xff0x@2405:6580:b080:900:64be:ce6a:a0a8:1563)
2024-09-20 14:11:09 +0200Blasius_(~Blasius@2.219.56.221) (Ping timeout: 260 seconds)
2024-09-20 14:10:34 +0200chiselfu1echiselfuse
2024-09-20 14:05:31 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Ping timeout: 264 seconds)
2024-09-20 14:00:34 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net)
2024-09-20 14:00:23 +0200ash3en(~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Ping timeout: 265 seconds)
2024-09-20 13:58:18 +0200tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2024-09-20 13:55:51 +0200ash3en(~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207)
2024-09-20 13:52:32 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Ping timeout: 272 seconds)
2024-09-20 13:46:34 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net)
2024-09-20 13:42:35 +0200Smiles(uid551636@id-551636.lymington.irccloud.com)
2024-09-20 13:32:54 +0200morb(~morb@108.41.100.120) (Ping timeout: 252 seconds)
2024-09-20 13:29:50 +0200Smiles(uid551636@id-551636.lymington.irccloud.com) (Quit: Connection closed for inactivity)
2024-09-20 13:24:25 +0200morb(~morb@108.41.100.120)
2024-09-20 13:19:31 +0200bliminse(~bliminse@user/bliminse)
2024-09-20 13:14:53 +0200 <Inst> or am i wrong here?
2024-09-20 13:13:01 +0200 <Inst> . and >=> also has the wrong fixity, i think, but you can't really fix it without losing laziness
2024-09-20 13:12:34 +0200 <Inst> well, not really, but whereas >> can be optimized, it's harder to optimize a >>= chain
2024-09-20 13:08:30 +0200 <Inst> tbh it can't be avoided due to laziness
2024-09-20 13:08:24 +0200 <Inst> term >>= foo >>= bar starts stacking space
2024-09-20 13:08:04 +0200 <Inst> come to think of it, does >>= leak?
2024-09-20 13:07:08 +0200tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2024-09-20 13:06:56 +0200potato44(uid421314@id-421314.lymington.irccloud.com) (Quit: Connection closed for inactivity)
2024-09-20 13:06:48 +0200flounders(~flounders@173.246.214.210)