2025/05/06

2025-05-06 00:02:12 +0200JuanDaugherty(~juan@user/JuanDaugherty) JuanDaugherty
2025-05-06 00:06:20 +0200Sgeo(~Sgeo@user/sgeo) Sgeo
2025-05-06 00:09:56 +0200 <haskellbridge> <Liamzee> oh, it's been a while since i abused *** and &&&, i've totally forgotten :(
2025-05-06 00:13:12 +0200 <haskellbridge> <Liamzee> zeroArrow is about empty? well, it's const empty
2025-05-06 00:14:53 +0200 <haskellbridge> <Liamzee> "TOML already has implementations in some of the most popular programming languages today... Haskell ..."
2025-05-06 00:14:55 +0200 <haskellbridge> <Liamzee> https://toml.io/en/
2025-05-06 00:14:58 +0200 <haskellbridge> <Liamzee> thanks tom!
2025-05-06 00:39:18 +0200la1n(~la1n@81.222.178.255) (Remote host closed the connection)
2025-05-06 00:39:43 +0200la1n(~la1n@81.222.178.255)
2025-05-06 00:41:01 +0200 <EvanR> tom's markup language
2025-05-06 00:53:27 +0200ttybitnik(~ttybitnik@user/wolper) (Quit: Fading out...)
2025-05-06 00:56:22 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Read error: Connection reset by peer)
2025-05-06 00:59:10 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-06 01:03:48 +0200 <JuanDaugherty> enwiki sez he's a billionaire
2025-05-06 01:04:14 +0200prdak(~Thunderbi@user/prdak) prdak
2025-05-06 01:08:18 +0200prdak(~Thunderbi@user/prdak) (Ping timeout: 244 seconds)
2025-05-06 01:08:55 +0200sprotte24(~sprotte24@p200300d16f2c120050457aa1052cddc8.dip0.t-ipconnect.de) (Quit: Leaving)
2025-05-06 01:09:46 +0200JuanDaugherty(~juan@user/JuanDaugherty) (Quit: praxis.meansofproduction.biz (juan@acm.org))
2025-05-06 01:09:54 +0200j1n37(~j1n37@user/j1n37) (Ping timeout: 260 seconds)
2025-05-06 01:09:58 +0200j1n37-(~j1n37@user/j1n37) j1n37
2025-05-06 01:30:23 +0200jespada(~jespada@r179-25-149-142.dialup.adsl.anteldata.net.uy) (Quit: My Mac has gone to sleep. ZZZzzz…)
2025-05-06 01:36:21 +0200michalz(~michalz@185.246.207.203) (Read error: Connection reset by peer)
2025-05-06 01:37:50 +0200Axma14181Axman6
2025-05-06 01:37:54 +0200michalz(~michalz@185.246.207.217)
2025-05-06 01:38:09 +0200 <monochrom> EvanR: haha that's brilliant
2025-05-06 01:42:29 +0200j1n37-(~j1n37@user/j1n37) (Ping timeout: 245 seconds)
2025-05-06 01:43:20 +0200 <monochrom> Hey that's very inspiring. Next time I make an infix operator and can't think of a better name, it's ^^^ then! data BinTree a = Nil | BinTree a :^^^: BinTree a
2025-05-06 01:43:32 +0200j1n37(~j1n37@user/j1n37) j1n37
2025-05-06 01:46:02 +0200Square2(~Square4@user/square) Square
2025-05-06 01:47:38 +0200 <monochrom> \∩/ ::: also works
2025-05-06 01:49:34 +0200Square(~Square@user/square) (Ping timeout: 260 seconds)
2025-05-06 01:51:17 +0200Tuplanolla(~Tuplanoll@91-159-69-59.elisa-laajakaista.fi) (Quit: Leaving.)
2025-05-06 01:52:20 +0200zmt01(~zmt00@user/zmt00) zmt00
2025-05-06 01:52:49 +0200greber_(~greber@82.148.184.53)
2025-05-06 01:53:07 +0200euleritian(~euleritia@dynamic-176-000-054-130.176.0.pool.telefonica.de) (Read error: Connection reset by peer)
2025-05-06 01:53:25 +0200euleritian(~euleritia@ip2504e858.dynamic.kabel-deutschland.de)
2025-05-06 01:54:53 +0200segfaultfizzbuzz(~segfaultf@23-93-74-222.fiber.dynamic.sonic.net) (Remote host closed the connection)
2025-05-06 01:55:26 +0200greber(~greber@82.148.184.53) (Ping timeout: 252 seconds)
2025-05-06 01:55:26 +0200swamp_(~zmt00@user/zmt00) (Ping timeout: 252 seconds)
2025-05-06 01:55:26 +0200finsternis(~X@23.226.237.192) (Ping timeout: 252 seconds)
2025-05-06 01:55:35 +0200segfaultfizzbuzz(~segfaultf@23-93-74-222.fiber.dynamic.sonic.net) segfaultfizzbuzz
2025-05-06 01:57:19 +0200finsternis(~X@23.226.237.192) finsternis
2025-05-06 02:06:26 +0200euleritian(~euleritia@ip2504e858.dynamic.kabel-deutschland.de) (Ping timeout: 252 seconds)
2025-05-06 02:06:47 +0200euleritian(~euleritia@dynamic-176-000-054-143.176.0.pool.telefonica.de)
2025-05-06 02:07:50 +0200Katarushisu(~Katarushi@finc-20-b2-v4wan-169598-cust1799.vm7.cable.virginm.net) (Ping timeout: 260 seconds)
2025-05-06 02:07:52 +0200euleritian(~euleritia@dynamic-176-000-054-143.176.0.pool.telefonica.de) (Read error: Connection reset by peer)
2025-05-06 02:08:09 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de)
2025-05-06 02:12:00 +0200xff0x(~xff0x@2405:6580:b080:900:2b75:7056:1970:c58f)
2025-05-06 02:15:28 +0200acidjnk_new3(~acidjnk@p200300d6e71c4f8221d365420023dfe1.dip0.t-ipconnect.de) (Ping timeout: 276 seconds)
2025-05-06 02:30:43 +0200Katarushisu(~Katarushi@finc-20-b2-v4wan-169598-cust1799.vm7.cable.virginm.net) Katarushisu
2025-05-06 02:35:02 +0200sajenim(~sajenim@user/sajenim) sajenim
2025-05-06 02:38:40 +0200xff0x(~xff0x@2405:6580:b080:900:2b75:7056:1970:c58f) (Ping timeout: 272 seconds)
2025-05-06 02:40:56 +0200xff0x(~xff0x@2405:6580:b080:900:bd8f:49eb:d362:d8a3)
2025-05-06 02:47:19 +0200Katarushisu(~Katarushi@finc-20-b2-v4wan-169598-cust1799.vm7.cable.virginm.net) (Ping timeout: 276 seconds)
2025-05-06 02:52:36 +0200greber_(~greber@82.148.184.53) (Remote host closed the connection)
2025-05-06 03:04:36 +0200Katarushisu(~Katarushi@finc-20-b2-v4wan-169598-cust1799.vm7.cable.virginm.net) Katarushisu
2025-05-06 03:12:40 +0200j1n37-(~j1n37@user/j1n37) j1n37
2025-05-06 03:12:48 +0200j1n37(~j1n37@user/j1n37) (Ping timeout: 252 seconds)
2025-05-06 03:25:19 +0200droideqa(uid499291@user/droideqa) (Quit: Connection closed for inactivity)
2025-05-06 03:28:34 +0200joeyadams(~textual@syn-162-154-010-038.res.spectrum.com)
2025-05-06 03:29:17 +0200j1n37(~j1n37@user/j1n37) j1n37
2025-05-06 03:29:57 +0200j1n37-(~j1n37@user/j1n37) (Ping timeout: 248 seconds)
2025-05-06 03:34:13 +0200machinedgod(~machinedg@d108-173-18-100.abhsia.telus.net) (Ping timeout: 248 seconds)
2025-05-06 03:36:51 +0200 <Square2> Re: "<monochrom> \∩/ ::: also works " <-- where is that function defined?
2025-05-06 03:39:00 +0200 <Square2> It's simple to roll your own, but I just assumed it would be in base somewhere
2025-05-06 04:14:18 +0200td_(~td@i5387090D.versanet.de) (Ping timeout: 244 seconds)
2025-05-06 04:16:05 +0200td_(~td@i53870907.versanet.de) td_
2025-05-06 04:20:49 +0200tabaqui(~tabaqui@167.71.80.236) (Ping timeout: 245 seconds)
2025-05-06 04:22:52 +0200td_(~td@i53870907.versanet.de) (Ping timeout: 276 seconds)
2025-05-06 04:24:21 +0200td_(~td@i5387093E.versanet.de) td_
2025-05-06 04:27:26 +0200 <monochrom> It is user-definable.
2025-05-06 05:01:51 +0200winniequinn(~winniequi@user/winniequinn) winniequinn
2025-05-06 05:07:59 +0200tavare(~tavare@user/tavare) tavare
2025-05-06 05:09:04 +0200tavare(~tavare@user/tavare) (Remote host closed the connection)
2025-05-06 05:12:48 +0200winniequinn(~winniequi@user/winniequinn) (Quit: nyaa~)
2025-05-06 05:17:01 +0200jmcantrell(~weechat@user/jmcantrell) (Ping timeout: 272 seconds)
2025-05-06 05:18:44 +0200jmcantrell(~weechat@user/jmcantrell) jmcantrell
2025-05-06 05:32:08 +0200jmcantrell(~weechat@user/jmcantrell) (Ping timeout: 252 seconds)
2025-05-06 05:35:27 +0200jmcantrell(~weechat@user/jmcantrell) jmcantrell
2025-05-06 05:35:27 +0200bitmapper(uid464869@id-464869.lymington.irccloud.com) bitmapper
2025-05-06 05:39:34 +0200jmcantrell(~weechat@user/jmcantrell) (Ping timeout: 245 seconds)
2025-05-06 05:41:47 +0200jmcantrell(~weechat@user/jmcantrell) jmcantrell
2025-05-06 05:44:19 +0200j1n37-(~j1n37@user/j1n37) j1n37
2025-05-06 05:44:32 +0200dutchie(~dutchie@user/dutchie) (Remote host closed the connection)
2025-05-06 05:45:05 +0200aforemny_(~aforemny@2001:9e8:6cc8:6800:9956:496f:fbf1:8d53) aforemny
2025-05-06 05:45:25 +0200j1n37(~j1n37@user/j1n37) (Ping timeout: 276 seconds)
2025-05-06 05:45:33 +0200dutchie(~dutchie@user/dutchie) dutchie
2025-05-06 05:46:04 +0200aforemny(~aforemny@2001:9e8:6ce9:ae00:f066:85cb:935a:63da) (Ping timeout: 276 seconds)
2025-05-06 06:01:07 +0200wootehfoot(~wootehfoo@user/wootehfoot) wootehfoot
2025-05-06 06:07:03 +0200wootehfoot(~wootehfoo@user/wootehfoot) (Ping timeout: 272 seconds)
2025-05-06 06:08:00 +0200prdak(~Thunderbi@user/prdak) prdak
2025-05-06 06:08:21 +0200Garbanzo(~Garbanzo@2602:304:6eac:dc10::46)
2025-05-06 06:12:43 +0200prdak(~Thunderbi@user/prdak) (Ping timeout: 276 seconds)
2025-05-06 06:22:11 +0200joeyadams(~textual@syn-162-154-010-038.res.spectrum.com) (Quit: Textual IRC Client: www.textualapp.com)
2025-05-06 06:22:28 +0200jmcantrell(~weechat@user/jmcantrell) (Ping timeout: 276 seconds)
2025-05-06 06:24:08 +0200jmcantrell(~weechat@user/jmcantrell) jmcantrell
2025-05-06 06:32:29 +0200talismanick(~user@2601:644:937c:ed10::ae5) (Ping timeout: 260 seconds)
2025-05-06 06:59:05 +0200werneta(~werneta@syn-071-083-160-242.res.spectrum.com) werneta
2025-05-06 07:00:23 +0200manwithluck(~manwithlu@2a09:bac5:5081:2dc::49:f6) (Remote host closed the connection)
2025-05-06 07:00:33 +0200manwithluck(~manwithlu@2a09:bac5:5081:2dc::49:f6) manwithluck
2025-05-06 07:03:30 +0200gorignak(~gorignak@user/gorignak) (Quit: quit)
2025-05-06 07:18:06 +0200takuan(~takuan@d8D86B601.access.telenet.be)
2025-05-06 07:27:16 +0200la1n(~la1n@81.222.178.255) (Read error: Connection reset by peer)
2025-05-06 07:29:06 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de) (Ping timeout: 252 seconds)
2025-05-06 07:30:02 +0200euleritian(~euleritia@dynamic-176-006-138-148.176.6.pool.telefonica.de)
2025-05-06 07:36:17 +0200euleritian(~euleritia@dynamic-176-006-138-148.176.6.pool.telefonica.de) (Read error: Connection reset by peer)
2025-05-06 07:36:36 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de)
2025-05-06 07:52:56 +0200hgolden(~hgolden@2603:8000:9d00:3ed1:88e0:76ff:fe9c:b21e) (Remote host closed the connection)
2025-05-06 08:01:55 +0200echoreply(~echoreply@45.32.163.16) (Quit: WeeChat 2.8)
2025-05-06 08:02:52 +0200echoreply(~echoreply@45.32.163.16) echoreply
2025-05-06 08:05:08 +0200hgolden(~hgolden@2603:8000:9d00:3ed1:88e0:76ff:fe9c:b21e) hgolden
2025-05-06 08:16:00 +0200prdak(~Thunderbi@user/prdak) prdak
2025-05-06 08:32:48 +0200prdak(~Thunderbi@user/prdak) (Read error: Connection reset by peer)
2025-05-06 08:33:25 +0200prdak(~Thunderbi@user/prdak) prdak
2025-05-06 08:33:51 +0200sord937(~sord937@gateway/tor-sasl/sord937) sord937
2025-05-06 08:36:28 +0200sord937(~sord937@gateway/tor-sasl/sord937) (Remote host closed the connection)
2025-05-06 08:36:47 +0200sord937(~sord937@gateway/tor-sasl/sord937) sord937
2025-05-06 08:39:20 +0200tromp(~textual@2001:1c00:3487:1b00:cdc3:f42b:30fc:1c61)
2025-05-06 08:41:00 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de) (Ping timeout: 276 seconds)
2025-05-06 08:42:53 +0200euleritian(~euleritia@dynamic-176-006-138-148.176.6.pool.telefonica.de)
2025-05-06 08:44:33 +0200jmcantrell(~weechat@user/jmcantrell) (Ping timeout: 248 seconds)
2025-05-06 08:49:38 +0200Garbanzo(~Garbanzo@2602:304:6eac:dc10::46) (Remote host closed the connection)
2025-05-06 08:57:51 +0200acidjnk_new3(~acidjnk@p200300d6e71c4f5329ce7e116cdf4532.dip0.t-ipconnect.de)
2025-05-06 09:00:00 +0200caconym7(~caconym@user/caconym) (Quit: bye)
2025-05-06 09:00:39 +0200caconym7(~caconym@user/caconym) caconym
2025-05-06 09:03:50 +0200__monty__(~toonn@user/toonn) toonn
2025-05-06 09:10:19 +0200JuanDaugherty(~juan@user/JuanDaugherty) JuanDaugherty
2025-05-06 09:19:32 +0200prdak(~Thunderbi@user/prdak) (Quit: prdak)
2025-05-06 09:19:54 +0200prdak(~Thunderbi@user/prdak) prdak
2025-05-06 09:20:40 +0200lortabac(~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4)
2025-05-06 09:26:12 +0200fp(~Thunderbi@wireless-86-50-140-117.open.aalto.fi) fp
2025-05-06 09:29:19 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Read error: Connection reset by peer)
2025-05-06 09:32:45 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-06 09:34:04 +0200m1dnight(~m1dnight@d8D861908.access.telenet.be) (Ping timeout: 252 seconds)
2025-05-06 09:34:28 +0200m1dnight(~m1dnight@d8D861908.access.telenet.be) m1dnight
2025-05-06 09:40:41 +0200 <[exa]> I'm getting a linker error when trying to build static binaries in github CI (on ubuntu-latest): "error: relocation refers to local symbol ".text" [1], which is defined in a discarded section". Did anyone see anything such? (mainly, any guess on where to start debugging?)
2025-05-06 09:41:02 +0200 <[exa]> locally it works OK (on debian tho, should I assume this to be ubuntu-caused weirdness?)
2025-05-06 09:43:01 +0200 <[exa]> (tail of the build log with the yuge link command here, if anyone enjoys reading these things: https://paste.tomsmeding.com/dac7Oswb )
2025-05-06 09:43:52 +0200emmanuelux(~emmanuelu@user/emmanuelux) (Read error: Connection reset by peer)
2025-05-06 09:51:24 +0200Sgeo(~Sgeo@user/sgeo) (Read error: Connection reset by peer)
2025-05-06 10:02:21 +0200hgolden(~hgolden@2603:8000:9d00:3ed1:88e0:76ff:fe9c:b21e) (Ping timeout: 252 seconds)
2025-05-06 10:02:21 +0200merijn(~merijn@77.242.116.146) merijn
2025-05-06 10:03:53 +0200hgolden(~hgolden@2603:8000:9d00:3ed1:88e0:76ff:fe9c:b21e) hgolden
2025-05-06 10:10:29 +0200acidjnk_new3(~acidjnk@p200300d6e71c4f5329ce7e116cdf4532.dip0.t-ipconnect.de) (Read error: Connection reset by peer)
2025-05-06 10:12:32 +0200 <tomsmeding> [exa]: did you see that warning about dlopen?
2025-05-06 10:13:08 +0200 <tomsmeding> and the 10 similar warnings below it
2025-05-06 10:13:12 +0200 <tomsmeding> lines 25-35
2025-05-06 10:13:20 +0200 <tomsmeding> oh and more lol
2025-05-06 10:13:34 +0200euleritian(~euleritia@dynamic-176-006-138-148.176.6.pool.telefonica.de) (Read error: Connection reset by peer)
2025-05-06 10:13:52 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de)
2025-05-06 10:14:07 +0200 <tomsmeding> [exa]: I'm not sure, but I wouldn't discard the possibility that this error depends on the glibc version
2025-05-06 10:14:35 +0200JuanDaughertyColinRobinson
2025-05-06 10:15:31 +0200 <tomsmeding> [exa]: but those warnings rather explicitly tell you that what you're trying to do isn't helpful
2025-05-06 10:15:37 +0200acidjnk(~acidjnk@p200300d6e71c4f53bcc85498df75fec7.dip0.t-ipconnect.de) acidjnk
2025-05-06 10:19:05 +0200tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net) (Quit: zzz)
2025-05-06 10:19:44 +0200prdak(~Thunderbi@user/prdak) (Read error: Connection reset by peer)
2025-05-06 10:19:48 +0200 <[exa]> tomsmeding: yeah, but otherwise it works perfectly despite the warnings :)
2025-05-06 10:20:15 +0200 <tomsmeding> because on the other system you have a compatible glibc version, presumably
2025-05-06 10:20:34 +0200 <tomsmeding> try running the executable on a musl system, or a system with a much older glibc than the one you built on
2025-05-06 10:20:52 +0200 <[exa]> ofc there it dies, that's ok
2025-05-06 10:21:06 +0200 <tomsmeding> ... but if you allow that, why do static linking of glibc in the first place
2025-05-06 10:22:00 +0200 <[exa]> can I somehow pick which libraries I want to have packed as static?
2025-05-06 10:23:02 +0200 <tomsmeding> with gcc, you can, apparently
2025-05-06 10:23:32 +0200 <tomsmeding> you're right that this may be hard or impossible through ghc
2025-05-06 10:23:40 +0200chele(~chele@user/chele) chele
2025-05-06 10:23:52 +0200CiaoSen(~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) CiaoSen
2025-05-06 10:24:23 +0200 <[exa]> kinda wondering, can I take the dynamic executable and just somehow pack some of the libraries to it?
2025-05-06 10:25:28 +0200 <tomsmeding> that's apparently hard
2025-05-06 10:25:38 +0200 <tomsmeding> https://unix.stackexchange.com/questions/685255/create-an-statically-linked-executable-from-a-dyna…
2025-05-06 10:25:56 +0200 <[exa]> whew https://github.com/sigurd-dev/mkblob
2025-05-06 10:28:56 +0200weary-traveler(~user@user/user363627) (Remote host closed the connection)
2025-05-06 10:29:10 +0200tromp(~textual@2001:1c00:3487:1b00:cdc3:f42b:30fc:1c61) (Quit: My iMac has gone to sleep. ZZZzzz…)
2025-05-06 10:29:28 +0200 <[exa]> well I guess I'll do the trick with LD_LIBRARY_PATH and some scriptage
2025-05-06 10:30:08 +0200 <tomsmeding> that is probably saner
2025-05-06 10:30:14 +0200fp(~Thunderbi@wireless-86-50-140-117.open.aalto.fi) (Read error: Connection reset by peer)
2025-05-06 10:30:17 +0200fp1(~Thunderbi@wireless-86-50-140-117.open.aalto.fi) fp
2025-05-06 10:30:23 +0200 <tomsmeding> than some random tool from an executable uploaded to github with "Add files for upload"
2025-05-06 10:30:34 +0200 <[exa]> true.
2025-05-06 10:32:34 +0200fp1fp
2025-05-06 10:52:08 +0200fp(~Thunderbi@wireless-86-50-140-117.open.aalto.fi) (Ping timeout: 244 seconds)
2025-05-06 11:09:40 +0200j1n37(~j1n37@user/j1n37) j1n37
2025-05-06 11:10:54 +0200j1n37-(~j1n37@user/j1n37) (Ping timeout: 265 seconds)
2025-05-06 11:12:45 +0200prdak(~Thunderbi@user/prdak) prdak
2025-05-06 11:15:34 +0200fp(~Thunderbi@wireless-86-50-140-117.open.aalto.fi) fp
2025-05-06 11:16:21 +0200michalz(~michalz@185.246.207.217) (Ping timeout: 252 seconds)
2025-05-06 11:17:50 +0200michalz(~michalz@185.246.207.221)
2025-05-06 11:19:40 +0200fp(~Thunderbi@wireless-86-50-140-117.open.aalto.fi) (Client Quit)
2025-05-06 11:19:44 +0200fp1(~Thunderbi@wireless-86-50-140-117.open.aalto.fi) fp
2025-05-06 11:22:03 +0200fp1fp
2025-05-06 11:25:27 +0200prdak(~Thunderbi@user/prdak) (Read error: Connection reset by peer)
2025-05-06 11:34:55 +0200tromp(~textual@2001:1c00:3487:1b00:cdc3:f42b:30fc:1c61)
2025-05-06 11:44:40 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de) (Ping timeout: 252 seconds)
2025-05-06 11:45:42 +0200euleritian(~euleritia@dynamic-176-006-138-148.176.6.pool.telefonica.de)
2025-05-06 12:02:37 +0200michalz(~michalz@185.246.207.221) (Ping timeout: 252 seconds)
2025-05-06 12:05:55 +0200fp(~Thunderbi@wireless-86-50-140-117.open.aalto.fi) (Ping timeout: 252 seconds)
2025-05-06 12:06:06 +0200fp(~Thunderbi@wireless-86-50-140-117.open.aalto.fi) fp
2025-05-06 12:06:30 +0200michalz(~michalz@185.246.207.218)
2025-05-06 12:08:46 +0200wootehfoot(~wootehfoo@user/wootehfoot) wootehfoot
2025-05-06 12:10:18 +0200lortabac(~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4) (Ping timeout: 276 seconds)
2025-05-06 12:12:51 +0200euleritian(~euleritia@dynamic-176-006-138-148.176.6.pool.telefonica.de) (Read error: Connection reset by peer)
2025-05-06 12:13:08 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de)
2025-05-06 12:24:50 +0200fp(~Thunderbi@wireless-86-50-140-117.open.aalto.fi) (Ping timeout: 244 seconds)
2025-05-06 12:25:41 +0200j1n37(~j1n37@user/j1n37) (Read error: Connection reset by peer)
2025-05-06 12:29:16 +0200j1n37(~j1n37@user/j1n37) j1n37
2025-05-06 12:33:06 +0200fp(~Thunderbi@2001:708:20:1406::10c5) fp
2025-05-06 12:35:14 +0200rvalue(~rvalue@user/rvalue) (Read error: Connection reset by peer)
2025-05-06 12:35:52 +0200rvalue(~rvalue@user/rvalue) rvalue
2025-05-06 12:36:29 +0200prdak(~Thunderbi@user/prdak) prdak
2025-05-06 12:44:28 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de) (Ping timeout: 244 seconds)
2025-05-06 12:45:44 +0200euleritian(~euleritia@77.23.248.100)
2025-05-06 12:50:28 +0200euleritian(~euleritia@77.23.248.100) (Ping timeout: 272 seconds)
2025-05-06 12:51:17 +0200euleritian(~euleritia@dynamic-176-006-138-148.176.6.pool.telefonica.de)
2025-05-06 12:51:29 +0200haritz(~hrtz@152.37.68.178)
2025-05-06 12:51:29 +0200haritz(~hrtz@152.37.68.178) (Changing host)
2025-05-06 12:51:29 +0200haritz(~hrtz@user/haritz) haritz
2025-05-06 12:55:51 +0200euleritian(~euleritia@dynamic-176-006-138-148.176.6.pool.telefonica.de) (Read error: Connection reset by peer)
2025-05-06 12:56:42 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de)
2025-05-06 12:58:52 +0200chele_(~chele@user/chele) chele
2025-05-06 13:00:05 +0200caconym7(~caconym@user/caconym) (Quit: bye)
2025-05-06 13:01:35 +0200chele(~chele@user/chele) (Ping timeout: 265 seconds)
2025-05-06 13:01:39 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de) (Ping timeout: 276 seconds)
2025-05-06 13:01:54 +0200michalz(~michalz@185.246.207.218) (Read error: Connection reset by peer)
2025-05-06 13:02:16 +0200caconym7(~caconym@user/caconym) caconym
2025-05-06 13:02:29 +0200lortabac(~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4)
2025-05-06 13:02:41 +0200euleritian(~euleritia@77.23.248.100)
2025-05-06 13:03:43 +0200michalz(~michalz@185.246.207.222)
2025-05-06 13:08:24 +0200wootehfoot(~wootehfoo@user/wootehfoot) (Read error: Connection reset by peer)
2025-05-06 13:09:20 +0200j1n37-(~j1n37@user/j1n37) j1n37
2025-05-06 13:09:25 +0200fp(~Thunderbi@2001:708:20:1406::10c5) (Quit: fp)
2025-05-06 13:09:48 +0200j1n37(~j1n37@user/j1n37) (Ping timeout: 265 seconds)
2025-05-06 13:10:41 +0200fp(~Thunderbi@2001:708:20:1406::10c5) fp
2025-05-06 13:11:17 +0200euleritian(~euleritia@77.23.248.100) (Ping timeout: 248 seconds)
2025-05-06 13:12:21 +0200euleritian(~euleritia@dynamic-176-006-138-148.176.6.pool.telefonica.de)
2025-05-06 13:22:29 +0200acidjnk(~acidjnk@p200300d6e71c4f53bcc85498df75fec7.dip0.t-ipconnect.de) (Ping timeout: 268 seconds)
2025-05-06 13:25:10 +0200acidjnk(~acidjnk@p200300d6e71c4f53e574b8a80288d07c.dip0.t-ipconnect.de) acidjnk
2025-05-06 13:28:27 +0200 <yin> which other popular languages feature automatic currying?
2025-05-06 13:28:34 +0200tabaqui(~tabaqui@167.71.80.236) tabaqui
2025-05-06 13:31:20 +0200 <tomsmeding> ocaml, presumably
2025-05-06 13:39:09 +0200 <tomsmeding> languages are generally not so deluded as to think that partially applying a function, and actually calling it, are similar operationally
2025-05-06 13:43:10 +0200j1n37-(~j1n37@user/j1n37) (Ping timeout: 276 seconds)
2025-05-06 13:44:21 +0200j1n37(~j1n37@user/j1n37) j1n37
2025-05-06 13:44:58 +0200 <[exa]> forth
2025-05-06 13:44:59 +0200[exa]runs
2025-05-06 13:46:28 +0200tromp(~textual@2001:1c00:3487:1b00:cdc3:f42b:30fc:1c61) (Quit: My iMac has gone to sleep. ZZZzzz…)
2025-05-06 13:50:51 +0200tromp(~textual@2001:1c00:3487:1b00:cdc3:f42b:30fc:1c61)
2025-05-06 14:00:46 +0200zmt00(~zmt00@user/zmt00) zmt00
2025-05-06 14:02:32 +0200zmt01(~zmt00@user/zmt00) (Ping timeout: 252 seconds)
2025-05-06 14:08:50 +0200tolgo(~Thunderbi@199.115.144.130)
2025-05-06 14:09:21 +0200tolgo(~Thunderbi@199.115.144.130) (Client Quit)
2025-05-06 14:17:03 +0200acidjnk(~acidjnk@p200300d6e71c4f53e574b8a80288d07c.dip0.t-ipconnect.de) (Read error: Connection reset by peer)
2025-05-06 14:21:25 +0200euleritian(~euleritia@dynamic-176-006-138-148.176.6.pool.telefonica.de) (Read error: Connection reset by peer)
2025-05-06 14:21:30 +0200prdak(~Thunderbi@user/prdak) (Read error: Connection reset by peer)
2025-05-06 14:21:42 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de)
2025-05-06 14:24:45 +0200acidjnk(~acidjnk@p200300d6e71c4f530114fa8f2e8a4c12.dip0.t-ipconnect.de) acidjnk
2025-05-06 14:28:10 +0200jespada(~jespada@r179-25-149-142.dialup.adsl.anteldata.net.uy) jespada
2025-05-06 14:29:39 +0200Square2(~Square4@user/square) (Ping timeout: 260 seconds)
2025-05-06 14:30:16 +0200ubert(~Thunderbi@2a02:8109:ab8a:5a00:70a8:360f:569f:e3f9) ubert
2025-05-06 14:37:07 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de) (Read error: Connection reset by peer)
2025-05-06 14:37:42 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de)
2025-05-06 14:51:36 +0200weary-traveler(~user@user/user363627) user363627
2025-05-06 14:53:59 +0200ttybitnik(~ttybitnik@user/wolper) ttybitnik
2025-05-06 14:56:38 +0200gorignak(~gorignak@user/gorignak) gorignak
2025-05-06 15:00:17 +0200comerijn(~merijn@77.242.116.146) merijn
2025-05-06 15:02:54 +0200merijn(~merijn@77.242.116.146) (Ping timeout: 260 seconds)
2025-05-06 15:03:46 +0200 <mauke> yin: I had a prototype implementation for Perl, but they didn't like my suggested f($x)($y) calling syntax :-(
2025-05-06 15:12:54 +0200j1n37-(~j1n37@user/j1n37) j1n37
2025-05-06 15:13:29 +0200j1n37(~j1n37@user/j1n37) (Ping timeout: 268 seconds)
2025-05-06 15:15:28 +0200AlexZenon(~alzenon@5.139.233.9) (Ping timeout: 265 seconds)
2025-05-06 15:17:03 +0200 <lortabac> I've just discovered that UTCTime doesn't enforce any invariant on the number of seconds in a day
2025-05-06 15:18:03 +0200 <lortabac> you can do for example (UTCTime date (secondsToDiffTime 1000000)) and it will gladly accept it
2025-05-06 15:18:18 +0200 <lortabac> and then it shows it as 2025-05-06 23:59:913660 UTC
2025-05-06 15:18:47 +0200 <tomsmeding> I mean, how can a data type enforce invariants
2025-05-06 15:19:06 +0200 <lortabac> by providing a smart constructor
2025-05-06 15:19:46 +0200 <lortabac> I don't know, it seems strange to me that you are allowed to create such a date
2025-05-06 15:20:02 +0200AlexZenon(~alzenon@5.139.233.9)
2025-05-06 15:20:49 +0200 <tomsmeding> you could (n `addUTCTime` UTCTime date 0)
2025-05-06 15:21:14 +0200 <tomsmeding> if wrapping is the behaviour that you want
2025-05-06 15:22:34 +0200 <lortabac> I already have a solution for my specific problem. I'm mostly wondering whether this is a good API for time
2025-05-06 15:23:04 +0200 <lortabac> and how an impossible date would behave in various scenarios and conversions
2025-05-06 15:23:24 +0200 <tomsmeding> 'time' itself seems to use utcTimeToPosixSeconds a lot
2025-05-06 15:23:50 +0200 <tomsmeding> but yeah, I agree that a smart constructor that implements wrapping behaviour would have been neater
2025-05-06 15:26:54 +0200 <yin> lortabac: the UTC standart itself does not enforce it
2025-05-06 15:27:04 +0200 <lortabac> if I do (posixSecondsToUTCTime $ utcTimeToPOSIXSeconds impossibleTime) it gives me the next day at 00:00:00
2025-05-06 15:27:59 +0200 <yin> lortabac: *standard. meaning if the future it's possible for us to add an arbitrary number of seconds to a day. we routinely have leap seconds
2025-05-06 15:28:21 +0200 <lortabac> yin: right, it makes sense
2025-05-06 15:28:38 +0200 <lortabac> still, utcTimeToPOSIXSeconds seems to enforce a limit
2025-05-06 15:29:25 +0200 <lortabac> I wonder if it handles leap seconds correctly
2025-05-06 15:30:11 +0200 <lortabac> posixDayLength is hard-coded as 86400 seconds
2025-05-06 15:30:25 +0200j1n37-(~j1n37@user/j1n37) (Ping timeout: 276 seconds)
2025-05-06 15:30:43 +0200 <yin> 100000 seconds is just about 11 days and a half. we've famously skipped 10 days in 1582 :)
2025-05-06 15:31:05 +0200j1n37(~j1n37@user/j1n37) j1n37
2025-05-06 15:31:25 +0200 <lortabac> :)
2025-05-06 15:31:26 +0200 <yin> or 11 days in 1752
2025-05-06 15:31:51 +0200 <yin> for the british empire
2025-05-06 15:32:33 +0200 <tomsmeding> lortabac: UTC does not include leap seconds
2025-05-06 15:32:40 +0200 <tomsmeding> uh
2025-05-06 15:32:42 +0200 <tomsmeding> that makes no sense
2025-05-06 15:32:47 +0200 <tomsmeding> a posix timestamp does not include leap seconds, there, that does
2025-05-06 15:33:32 +0200 <tomsmeding> that means that conversion between UTC time and a POSIX timestamp does not need to care about leap seconds
2025-05-06 15:33:43 +0200 <df> I thought it was TAI that didn't include leap seconds
2025-05-06 15:34:06 +0200 <df> but I've no idea which one posix timestamps are based on
2025-05-06 15:34:24 +0200 <tomsmeding> iirc TAI just trudges on, regardless of what we pesky humans do with calendars and leap seconds
2025-05-06 15:34:43 +0200 <tomsmeding> whereas UTC actually intends to match what humans do, so when there's a leap second, you have two seconds with the same UTC time
2025-05-06 15:34:53 +0200 <tomsmeding> (after wrapping, perhaps)
2025-05-06 15:35:03 +0200 <tomsmeding> POSIX timestamps match UTC
2025-05-06 15:35:19 +0200 <yin> tomsmeding: that's not true
2025-05-06 15:35:30 +0200 <yin> no 2 seconds have the same timestamp in UTC
2025-05-06 15:35:35 +0200tomsmedingshould probably have looked things up
2025-05-06 15:35:42 +0200 <df> tbh I'm not sure if posix has been updated to be 64 bit
2025-05-06 15:36:04 +0200 <tomsmeding> yin: so what happens at a leap second, do you get :60 in the UTC time?
2025-05-06 15:36:16 +0200 <yin> yes
2025-05-06 15:36:29 +0200 <tomsmeding> https://en.wikipedia.org/wiki/Leap_second#Binary_representation
2025-05-06 15:36:40 +0200 <lortabac> so in this sense UTCTime is right in not wrapping
2025-05-06 15:36:43 +0200 <tomsmeding> yin: fair correction, but does not change my conclusion
2025-05-06 15:36:52 +0200 <lortabac> but then utcTimeToPosixSeconds is wrong
2025-05-06 15:37:13 +0200CiaoSen(~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) (Ping timeout: 265 seconds)
2025-05-06 15:37:41 +0200 <yin> hence my comments about how the permissive UTCTime implementation makes sense
2025-05-06 15:38:01 +0200 <tomsmeding> lortabac: POSIX does not count leap seconds, so as long as you only use the additional freedom in UTCTime to set the seconds field to 60 in case of a leap second, utcTimeToPosixSeconds is actually correct
2025-05-06 15:38:18 +0200 <yin> lortabac: Posix time does not account for leap seconds
2025-05-06 15:38:27 +0200 <yin> exactly
2025-05-06 15:38:41 +0200 <tomsmeding> if you set the seconds field to some other value then you're inputting a non-existent UTC time, and utcTimeToPosixSeconds... something
2025-05-06 15:38:52 +0200 <tomsmeding> s/something/does something/
2025-05-06 15:39:40 +0200 <tomsmeding> though this means that utcTimeToPosixSeconds is apparently (according to wikipedia) inconsistent with Linux: > Some computer operating systems, in particular Linux, assign to the leap second the counter value of the preceding, 23:59:59 second (59–59–0 sequence)
2025-05-06 15:40:01 +0200 <tomsmeding> (see the link I just posted)
2025-05-06 15:40:48 +0200 <yin> sometimes i wonder how useful this time thing we invented really is
2025-05-06 15:40:56 +0200 <lortabac> utcTimeToPosixSeconds uses the 59–0–0 sequence
2025-05-06 15:43:02 +0200 <lortabac> maybe it would be simpler to have N months of fixed length + a final month that ends when the solar year ends
2025-05-06 15:43:20 +0200 <yin> this is actually a question i like to ask people. how important do you feel, in a profession setting, synchronoyus communication is?
2025-05-06 15:44:00 +0200 <tomsmeding> it's important to have it available -- some things are best discussed synchronously
2025-05-06 15:44:13 +0200 <lortabac> sometimes it's important
2025-05-06 15:45:59 +0200 <yin> i get from "it's so unprofessional when i try to call a colleague at 9:01 and they don't answer because they're late" to "i don't answer phones at work and it's rude to interrupt other people's flow because whatever you need from me, you can ask it in an email"
2025-05-06 15:47:33 +0200 <lortabac> regarding phone, I just never answer :)
2025-05-06 15:48:32 +0200 <lortabac> but for example in case of an incident I set up a war room to discuss synchronously, because time matters in that case
2025-05-06 15:48:59 +0200 <yin> tomsmeding: i agree. but then you can arrange for a meeting "when the sun hits the sidewalk" or some universal time that doesn't have to be this mess
2025-05-06 15:49:39 +0200 <haskellbridge> <maerwald> if you work with other engineers on the same thing, you better have synchronous ad-hoc communication
2025-05-06 15:51:05 +0200 <haskellbridge> <maerwald> what I don't like is when people don't reply to my PR comments, unless I call them on facetime or whatever... stop being lazy
2025-05-06 15:51:09 +0200 <yin> haskellbridge: maerwald: github does a good enough job at getting around that
2025-05-06 15:51:21 +0200 <haskellbridge> <maerwald> no
2025-05-06 15:51:51 +0200 <yin> did i just ping haskellbridge? :p
2025-05-06 15:51:57 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de) (Ping timeout: 276 seconds)
2025-05-06 15:51:59 +0200 <haskellbridge> <maerwald> pair programming, brainstorming together, etc. does not work on github
2025-05-06 15:52:07 +0200euleritian(~euleritia@dynamic-176-006-138-148.176.6.pool.telefonica.de)
2025-05-06 15:52:27 +0200 <yin> true
2025-05-06 15:52:41 +0200 <tomsmeding> yin: I never connected messy UTC time to synchronous communication :p
2025-05-06 15:52:59 +0200 <tomsmeding> and in any case, if there is a connection, it's between messy time and _planning_
2025-05-06 15:53:06 +0200 <tomsmeding> the communication itself is separate
2025-05-06 15:53:18 +0200tomsmedingwill be afk for a while
2025-05-06 15:53:32 +0200 <haskellbridge> <maerwald> but collaboration in professional setting is mostly dead... people always get pieces of work that they can implement independently and then every team member gets their epics and your grind on your own without any real design or code collaboration
2025-05-06 15:53:42 +0200 <haskellbridge> <maerwald> programming is boring this way
2025-05-06 15:54:02 +0200 <yin> tomsmeding: oh i mean "time" in general
2025-05-06 15:54:52 +0200 <yin> like the need for two people to independently agree on "what time it is now"
2025-05-06 15:55:12 +0200 <yin> messy UTC is just a result of that
2025-05-06 15:56:39 +0200 <yin> maerwald: i have come to accept that programming is boring any way
2025-05-06 15:57:30 +0200 <haskellbridge> <maerwald> time for a career change
2025-05-06 15:57:58 +0200 <yin> there's that concept again
2025-05-06 15:58:25 +0200 <haskellbridge> <maerwald> you can become an LLM input engineer
2025-05-06 15:58:32 +0200 <df> yin: easily solved, I looked up the time earlier and wrote it down
2025-05-06 15:58:59 +0200 <df> it's 11:27:23 AM
2025-05-06 16:00:24 +0200 <yin> df: ok i wrote it down too
2025-05-06 16:00:46 +0200 <df> ok, so we're sychronised, problem solved ;)
2025-05-06 16:00:49 +0200 <yin> i'm also telling all my contacts
2025-05-06 16:01:01 +0200 <yin> wait
2025-05-06 16:01:03 +0200danza(~danza@user/danza) danza
2025-05-06 16:01:20 +0200 <yin> done. they also wrote it down and will spread the word
2025-05-06 16:01:30 +0200 <yin> we'll all be on the same time... soon
2025-05-06 16:02:03 +0200danza(~danza@user/danza) (Remote host closed the connection)
2025-05-06 16:02:08 +0200 <df> good work, we can synchronise the entire world if we try
2025-05-06 16:02:13 +0200 <df> time is an illusion anyway
2025-05-06 16:05:09 +0200 <yin> won't we miss async communication though? oh no what have we done?
2025-05-06 16:05:47 +0200 <df> ... c'mon, somebody's gotta complete the douglas adams quote
2025-05-06 16:06:16 +0200hughjfchen(~hughjfche@vmi2417424.contaboserver.net) (Ping timeout: 244 seconds)
2025-05-06 16:07:08 +0200comerijn(~merijn@77.242.116.146) (Read error: Connection reset by peer)
2025-05-06 16:07:26 +0200merijn(~merijn@77.242.116.146) merijn
2025-05-06 16:07:33 +0200hughjfchen(~hughjfche@vmi2417424.contaboserver.net) hughjfchen
2025-05-06 16:08:15 +0200 <df> yin: made life easier for a bunch of programmers? ordering events might be tricky though, I admit
2025-05-06 16:08:25 +0200 <yin> "quickly, there's no time!"
2025-05-06 16:08:25 +0200 <yin> wait no, that was Doc Brown
2025-05-06 16:09:08 +0200 <df> but time has never been very reliable for that anyway, that's why we invented vector clocks etc
2025-05-06 16:16:10 +0200euleritian(~euleritia@dynamic-176-006-138-148.176.6.pool.telefonica.de) (Read error: Connection reset by peer)
2025-05-06 16:16:27 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de)
2025-05-06 16:19:43 +0200vanishingideal(~vanishing@user/vanishingideal) vanishingideal
2025-05-06 16:25:06 +0200ColinRobinson(~juan@user/JuanDaugherty) (Quit: praxis.meansofproduction.biz (juan@acm.org))
2025-05-06 16:32:54 +0200tromp(~textual@2001:1c00:3487:1b00:cdc3:f42b:30fc:1c61) (Quit: My iMac has gone to sleep. ZZZzzz…)
2025-05-06 16:40:37 +0200fp(~Thunderbi@2001:708:20:1406::10c5) (Ping timeout: 276 seconds)
2025-05-06 16:54:01 +0200vanishingideal(~vanishing@user/vanishingideal) (Ping timeout: 244 seconds)
2025-05-06 16:55:59 +0200ttybitnik(~ttybitnik@user/wolper) (Quit: Fading out...)
2025-05-06 17:04:44 +0200tromp(~textual@2001:1c00:3487:1b00:cdc3:f42b:30fc:1c61)
2025-05-06 17:06:41 +0200connrs(~connrs@user/connrs) connrs
2025-05-06 17:11:16 +0200 <haskellbridge> <Liamzee> things that happen to you in life:
2025-05-06 17:11:50 +0200 <haskellbridge> <Liamzee> "When you realize that Gabriella Gonzalez's haskellforall.com blog is actually a pun on explicit universal quantification"
2025-05-06 17:13:01 +0200 <haskellbridge> <Liamzee> had a disaster with LLM just now, I was looking for Haskell-themed website names, oriented around the arrow from the initial object
2025-05-06 17:13:47 +0200 <haskellbridge> <Liamzee> Claude and Deepseek convinced me and each other that Zeromorph was a good name, when it refers to a constant and co-constant morphism. facepalm
2025-05-06 17:17:43 +0200Lord_of_Life(~Lord@user/lord-of-life/x-2819915) Lord_of_Life
2025-05-06 17:22:00 +0200 <haskellbridge> <Liamzee> dotmorphism is okay?
2025-05-06 17:22:00 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de) (Read error: Connection reset by peer)
2025-05-06 17:22:49 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de)
2025-05-06 17:27:08 +0200lortabac(~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4) (Quit: WeeChat 4.5.2)
2025-05-06 17:32:12 +0200lbseale(~quassel@user/ep1ctetus) ep1ctetus
2025-05-06 17:32:12 +0200tv(~tv@user/tv) (Read error: Connection reset by peer)
2025-05-06 17:32:45 +0200jespada_(~jespada@r179-24-30-150.dialup.adsl.anteldata.net.uy) jespada
2025-05-06 17:33:14 +0200JuanDaugherty(~juan@user/JuanDaugherty) JuanDaugherty
2025-05-06 17:35:12 +0200jespada(~jespada@r179-25-149-142.dialup.adsl.anteldata.net.uy) (Ping timeout: 252 seconds)
2025-05-06 17:45:42 +0200chele_(~chele@user/chele) (Ping timeout: 276 seconds)
2025-05-06 17:49:27 +0200adamCS(~adamCS@70.19.85.77) (Remote host closed the connection)
2025-05-06 17:50:56 +0200adamCS(~adamCS@70.19.85.77) adamCS
2025-05-06 17:54:35 +0200acidjnk(~acidjnk@p200300d6e71c4f530114fa8f2e8a4c12.dip0.t-ipconnect.de) (Ping timeout: 260 seconds)