2026/06/03

Newest at the top

2026-06-03 17:18:15 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-06-03 17:17:29 +0000emilym(~Thunderbi@user/emilym) emilym
2026-06-03 17:15:47 +0000bggd_(~bgg@2a01:e0a:fd5:f510:dfb:7180:26ed:4cfc) (Remote host closed the connection)
2026-06-03 17:07:11 +0000 <yin> monochrom: fair point
2026-06-03 17:04:53 +0000 <monochrom> yin: I use lazy lists because I want a O(1)-space algorithm so I am behaving like memory is expensive. And laziness adds constant checking of "is this evaluated yet? again?" so I guess I also behave like computation is cheap.
2026-06-03 17:03:46 +0000Wygulmage(~Wygulmage@user/Wygulmage) (Quit: Client closed)
2026-06-03 17:03:40 +0000tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net)
2026-06-03 17:03:30 +0000emilym1(~Thunderbi@user/emilym) (Ping timeout: 245 seconds)
2026-06-03 17:00:13 +0000emilym(~Thunderbi@user/emilym) (Ping timeout: 272 seconds)
2026-06-03 16:59:22 +0000emilym1(~Thunderbi@user/emilym) emilym
2026-06-03 16:48:16 +0000Googulator(~Googulato@193-226-241-87.pool.digikabel.hu)
2026-06-03 16:47:59 +0000Googulator(~Googulato@193-226-241-87.pool.digikabel.hu) (Quit: Client closed)
2026-06-03 16:43:04 +0000ricardomaps(~ricardoma@2804:14d:a040:81ea:d486:76c:2049:b6b5)
2026-06-03 16:39:07 +0000szkl(uid110435@id-110435.uxbridge.irccloud.com) (Quit: Connection closed for inactivity)
2026-06-03 16:31:43 +0000euphores(~SASL_euph@user/euphores) euphores
2026-06-03 16:30:48 +0000 <bitmapper> regardless there's always cachegrind
2026-06-03 16:30:20 +0000 <bitmapper> the garbage collector also tends to get you better cache locality than you would expect
2026-06-03 16:24:19 +0000merijn(~merijn@77.242.116.146) (Ping timeout: 264 seconds)
2026-06-03 16:23:27 +0000myme(~myme@55a506e8.bb.online.no) myme
2026-06-03 16:21:35 +0000myme(~myme@2001:4656:2f1b:0:719f:bfdf:da25:d03a) (Ping timeout: 272 seconds)
2026-06-03 16:21:30 +0000euphores(~SASL_euph@user/euphores) (Quit: Leaving.)
2026-06-03 16:11:05 +0000 <kuribas> yin: so you can have cache locality at the lower level.
2026-06-03 16:09:59 +0000 <kuribas> yin: "idiomatic haskell" means you create efficient (ugly) low level code, then make a combinator language on top that hides the complexity and ugliness, but still giving you expressivity.
2026-06-03 16:07:09 +0000superbil(~superbil@114-32-231-70.hinet-ip.hinet.net) superbil
2026-06-03 16:06:51 +0000superbil(~superbil@114-32-231-70.hinet-ip.hinet.net) (Client Quit)
2026-06-03 16:05:00 +0000superbil(~superbil@114-32-231-70.hinet-ip.hinet.net) superbil
2026-06-03 16:01:11 +0000superbil(~superbil@114-32-231-70.hinet-ip.hinet.net) (Quit: WeeChat 4.9.0)
2026-06-03 15:58:02 +0000Square2(~Square@user/square) (Ping timeout: 257 seconds)
2026-06-03 15:55:47 +0000pavonia(~user@user/siracusa) (Quit: Bye!)
2026-06-03 15:46:41 +0000detroitoit_(~detroitoi@91-150-198-77.dynamic.play.pl) (Remote host closed the connection)
2026-06-03 15:45:30 +0000emilym(~Thunderbi@user/emilym) emilym
2026-06-03 15:32:28 +0000merijn(~merijn@77.242.116.146) merijn
2026-06-03 15:31:22 +0000merijn(~merijn@77.242.116.150) (Read error: Connection reset by peer)
2026-06-03 15:29:59 +0000comerijn(~merijn@77.242.116.146) (Ping timeout: 249 seconds)
2026-06-03 15:29:52 +0000emilym(~Thunderbi@user/emilym) (Ping timeout: 276 seconds)
2026-06-03 15:28:41 +0000 <Wygulmage> Thanks!
2026-06-03 15:27:28 +0000merijn(~merijn@77.242.116.150) merijn
2026-06-03 15:26:52 +0000yin(~zero@user/zero) zero
2026-06-03 15:26:12 +0000 <int-e> there are no rules from fromIntegral though because it gets inlined. https://gitlab.haskell.org/ghc/ghc/-/blob/master/libraries/ghc-internal/src/GHC/Internal/Bignum/In… explains this for Int -> Word
2026-06-03 15:24:13 +0000yin(~zero@user/zero) (Remote host closed the connection)
2026-06-03 15:23:33 +0000ft(~ft@p4fc2aedc.dip0.t-ipconnect.de) ft
2026-06-03 15:23:12 +0000 <Wygulmage> Currently I get the warning "'fromIntegral' might inline first".
2026-06-03 15:22:35 +0000 <dolio> Like, `fromIntegral :: Int -> Word` has a rule to make it some int2word wrapper or something.
2026-06-03 15:21:16 +0000 <dolio> It is possible. I think a lot of the basic numeric types have rules like that.
2026-06-03 15:21:05 +0000Googulator(~Googulato@193-226-241-87.pool.digikabel.hu)
2026-06-03 15:20:49 +0000Googulator(~Googulato@193-226-241-87.pool.digikabel.hu) (Quit: Client closed)
2026-06-03 15:20:37 +0000spew(~spew@user/spew) spew
2026-06-03 15:20:26 +0000spew(~spew@user/spew) (Quit: spew)
2026-06-03 15:19:47 +0000eron(~eron@200-158-12-57.dsl.telesp.net.br) (Quit: Client closed)
2026-06-03 15:18:32 +0000 <Wygulmage> There's an enigmatic comment in GHC.Internal.Real that points to another comment in GHC.Core.Opt.ConstantFold that no longer exists.