2025/11/15

Newest at the top

2025-11-15 22:13:14 +0100haltingsolver(~cmo@2604:3d09:207f:8000::d1dc) (Ping timeout: 256 seconds)
2025-11-15 22:11:28 +0100trickard_trickard
2025-11-15 22:07:16 +0100weary-traveler(~user@user/user363627) user363627
2025-11-15 21:59:01 +0100saurcron(uid575716@user/saurcron) (Quit: Connection closed for inactivity)
2025-11-15 21:55:46 +0100Googulator34(~Googulato@2a01-036d-0106-0180-4475-80b4-5cdc-43d6.pool6.digikabel.hu) (Quit: Client closed)
2025-11-15 21:55:45 +0100Googulator91(~Googulato@2a01-036d-0106-0180-4475-80b4-5cdc-43d6.pool6.digikabel.hu)
2025-11-15 21:54:37 +0100wootehfoot(~wootehfoo@user/wootehfoot) wootehfoot
2025-11-15 21:51:27 +0100haltingsolver(~cmo@2604:3d09:207f:8000::d1dc)
2025-11-15 21:47:03 +0100califax_califax
2025-11-15 21:46:57 +0100Square3(~Square@user/square) (Ping timeout: 250 seconds)
2025-11-15 21:46:10 +0100califax(~califax@user/califx) (Ping timeout: 272 seconds)
2025-11-15 21:45:46 +0100califax_(~califax@user/califx) califx
2025-11-15 21:43:18 +0100geekosaur-o geekosaur
2025-11-15 21:42:38 +0100jmcantrell(~weechat@user/jmcantrell) jmcantrell
2025-11-15 21:36:05 +0100 <jreicher> the sort of object that should be given to the usual story of *, but if we ignore that story what happened is perfectly fine, because abstractions are not commutative.
2025-11-15 21:36:05 +0100 <jreicher> dolio: I take your point (two points, really), but I don't think it's like fixing evaluation order any more than the normal lambda calculus is. I think it's a confusion in the story we are telling about types and arguments. Take, for example, in a Church-numeral arithmetic, that we would probably have (* 0 (K 5)) -> 0, but (* (K 5) 0) -> 5 (or maybe (K (K 5)), etc. depending on implementation of *). What's going on here is (K 5) is not
2025-11-15 21:35:39 +0100Googulator34(~Googulato@2a01-036d-0106-0180-4475-80b4-5cdc-43d6.pool6.digikabel.hu)
2025-11-15 21:35:27 +0100Googulator34(~Googulato@2a01-036d-0106-0180-4475-80b4-5cdc-43d6.pool6.digikabel.hu) (Quit: Client closed)
2025-11-15 21:27:32 +0100 <geekosaur> I opped up because they're working on services. But I'm a little busy so ping me if needed
2025-11-15 21:25:50 +0100Googulator89(~Googulato@2a01-036d-0106-0180-4475-80b4-5cdc-43d6.pool6.digikabel.hu) (Quit: Client closed)
2025-11-15 21:25:50 +0100Googulator34(~Googulato@2a01-036d-0106-0180-4475-80b4-5cdc-43d6.pool6.digikabel.hu)
2025-11-15 21:24:04 +0100CiaoSen(~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) CiaoSen
2025-11-15 21:21:22 +0100ChanServ+o geekosaur
2025-11-15 21:20:39 +0100Googulator89(~Googulato@2a01-036d-0106-0180-4475-80b4-5cdc-43d6.pool6.digikabel.hu)
2025-11-15 21:20:35 +0100Googulator11(~Googulato@2a01-036d-0106-0180-4475-80b4-5cdc-43d6.pool6.digikabel.hu) (Quit: Client closed)
2025-11-15 21:20:02 +0100spew(~spew@user/spew) spew
2025-11-15 21:10:47 +0100Googulator70(~Googulato@2a01-036d-0106-0180-4475-80b4-5cdc-43d6.pool6.digikabel.hu) (Quit: Client closed)
2025-11-15 21:10:43 +0100Googulator11(~Googulato@2a01-036d-0106-0180-4475-80b4-5cdc-43d6.pool6.digikabel.hu)
2025-11-15 21:08:53 +0100Lycurgus(~juan@user/Lycurgus) (Quit: alsoknownas.renjuan.org ( juan@acm.org ))
2025-11-15 20:53:17 +0100target_i(~target_i@user/target-i/x-6023099) target_i
2025-11-15 20:52:39 +0100DragonMaus(~dragonmau@user/dragonmaus) DragonMaus
2025-11-15 20:51:51 +0100DragonMaus(~dragonmau@user/dragonmaus) (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)
2025-11-15 20:48:37 +0100Digit(~user@user/digit) Digit
2025-11-15 20:47:15 +0100sindu(~sindu@77.19.134.151.tmi.telenormobil.no)
2025-11-15 20:47:07 +0100Digit(~user@user/digit) (Read error: Connection reset by peer)
2025-11-15 20:47:05 +0100ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 256 seconds)
2025-11-15 20:45:29 +0100GdeVolpi1(~GdeVolpia@user/GdeVolpiano) GdeVolpiano
2025-11-15 20:44:55 +0100GdeVolpi1(~GdeVolpia@user/GdeVolpiano) (Ping timeout: 245 seconds)
2025-11-15 20:44:43 +0100gorignak(~gorignak@user/gorignak) (Quit: quit)
2025-11-15 20:42:50 +0100ljdarj(~Thunderbi@user/ljdarj) ljdarj
2025-11-15 20:41:35 +0100simplystuart(~simplystu@c-75-75-152-164.hsd1.pa.comcast.net)
2025-11-15 20:40:45 +0100jmcantrell(~weechat@user/jmcantrell) (Ping timeout: 244 seconds)
2025-11-15 20:39:19 +0100 <haskellbridge> <sm> great links, thank you
2025-11-15 20:37:41 +0100paddymahoney(~paddymaho@pool-99-250-10-137.cpe.net.cable.rogers.com)
2025-11-15 20:37:13 +0100wootehfoot(~wootehfoo@user/wootehfoot) (Ping timeout: 264 seconds)
2025-11-15 20:35:46 +0100haltingsolver(~cmo@2604:3d09:207f:8000::d1dc) (Ping timeout: 256 seconds)
2025-11-15 20:34:21 +0100paddymahoney(~paddymaho@pool-99-250-10-137.cpe.net.cable.rogers.com) (Read error: Connection reset by peer)
2025-11-15 20:34:01 +0100 <haskellbridge> <sm> for context: the entertaining https://www.youtube.com/watch?v=BhaBzbzEbKg video struggled to bring C structs across the FFI boundary and I wondered what's current best practice, and magic_rb pointed me to hs-bindgen
2025-11-15 20:32:31 +0100 <int-e> (voting for name collision)
2025-11-15 20:32:09 +0100 <int-e> https://github.com/well-typed/hs-bindgen looks quite different from https://github.com/yvan-sraka/hs-bindgen