2024/11/08

Newest at the top

2024-11-08 14:51:55 +0100dontdieych2_(~quassel@user/dontdieych2) dontdieych2
2024-11-08 14:51:41 +0100dontdieych2(~quassel@user/dontdieych2) dontdieych2
2024-11-08 14:50:37 +0100AwoobisgAy_Dragon
2024-11-08 14:50:23 +0100euleritian(~euleritia@77.22.252.56)
2024-11-08 14:50:05 +0100euleritian(~euleritia@dynamic-176-007-148-106.176.7.pool.telefonica.de) (Read error: Connection reset by peer)
2024-11-08 14:47:33 +0100euleritian(~euleritia@dynamic-176-007-148-106.176.7.pool.telefonica.de)
2024-11-08 14:46:47 +0100euleritian(~euleritia@dynamic-176-006-140-137.176.6.pool.telefonica.de) (Ping timeout: 255 seconds)
2024-11-08 14:38:58 +0100hughjfchen(~hughjfche@vmi556545.contaboserver.net) hughjfchen
2024-11-08 14:38:27 +0100sourcetarius(~sourcetar@user/sourcetarius) (Quit: sourcetarius)
2024-11-08 14:37:41 +0100euleritian(~euleritia@dynamic-176-006-140-137.176.6.pool.telefonica.de)
2024-11-08 14:36:48 +0100euleritian(~euleritia@77.22.252.56) (Ping timeout: 252 seconds)
2024-11-08 14:34:48 +0100weary-traveler(~user@user/user363627) (Remote host closed the connection)
2024-11-08 14:33:37 +0100L29Ah(~L29Ah@wikipedia/L29Ah) (Ping timeout: 248 seconds)
2024-11-08 14:33:00 +0100sand-witch(~m-mzmz6l@vmi833741.contaboserver.net)
2024-11-08 14:30:39 +0100hughjfchen(~hughjfche@vmi556545.contaboserver.net) (Ping timeout: 260 seconds)
2024-11-08 14:29:02 +0100sand-witch(~m-mzmz6l@vmi833741.contaboserver.net) (Remote host closed the connection)
2024-11-08 14:27:50 +0100Smiles(uid551636@id-551636.lymington.irccloud.com) (Quit: Connection closed for inactivity)
2024-11-08 14:21:43 +0100rvalue-rvalue
2024-11-08 14:16:06 +0100ash3en(~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Ping timeout: 276 seconds)
2024-11-08 14:14:29 +0100rvalue(~rvalue@user/rvalue) (Ping timeout: 248 seconds)
2024-11-08 14:13:49 +0100rvalue-(~rvalue@user/rvalue) rvalue
2024-11-08 14:13:27 +0100manwithluck(manwithluc@gateway/vpn/protonvpn/manwithluck) manwithluck
2024-11-08 14:08:31 +0100manwithluck(manwithluc@gateway/vpn/protonvpn/manwithluck) (Remote host closed the connection)
2024-11-08 14:08:19 +0100mceresa(~mceresa@user/mceresa) mceresa
2024-11-08 14:07:14 +0100BolzmannPain(~BolzmannP@user/BolzmannPain) (Quit: Client closed)
2024-11-08 14:03:14 +0100 <yin> maybe i abuse record updating
2024-11-08 14:01:38 +0100ash3en(~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) ash3en
2024-11-08 14:01:14 +0100 <yin> i guess i'm thinking about the performance of product types in general comparing to, say, HashMap
2024-11-08 14:00:21 +0100ih1d(~ih1d@24.139.109.18) (Client Quit)
2024-11-08 13:59:04 +0100ih1d(~ih1d@24.139.109.18)
2024-11-08 13:57:57 +0100 <Leary> yin: It's a matter of interface, not representation. With regular product types, you only have positional notation for manipulating contained values. Records just let you specify them with names instead.
2024-11-08 13:57:45 +0100 <Rembane> yin: As product types plus some functions. Like the `data` types with many arguments without the record stuff.
2024-11-08 13:57:39 +0100 <opqdonut> but I have no idea what GHC actually does
2024-11-08 13:57:13 +0100 <opqdonut> I wouldn't expect using or not using record syntax to affect the runtime characteristics
2024-11-08 13:57:06 +0100BolzmannPain(~BolzmannP@user/BolzmannPain) BolzmannPain
2024-11-08 13:56:57 +0100poscat(~poscat@user/poscat) poscat
2024-11-08 13:56:39 +0100 <yin> Rembane: yes but how is their structure implemented internally?
2024-11-08 13:54:21 +0100alexherbo2(~alexherbo@2a02-8440-3309-f88a-dc43-ac5e-6a5b-79bd.rev.sfr.net) alexherbo2
2024-11-08 13:54:13 +0100poscat(~poscat@user/poscat) (Quit: Bye)
2024-11-08 13:53:22 +0100 <Rembane> yin: IIRC it's syntactic sugar for not having to write out all the access functions and save functions for a datatype.
2024-11-08 13:52:24 +0100 <kqr> Text.Printf does not come with an instance for Text. When I poke around I see some suggestions to use Data.Text.Format instead. Is this actually preferred? I find very little comparison online. The use case is not large templating but creating a Show instance for a custom numeric type – so I'm hesitant to reach for something that's not in base.
2024-11-08 13:52:04 +0100 <yin> philosophically, are records just a data structure that we give the compiler permission to optimize however it sees fit or is there something more to it?
2024-11-08 13:51:33 +0100mceresa(~mceresa@user/mceresa) (Read error: error:0A000119:SSL routines::decryption failed or bad record mac)
2024-11-08 13:47:09 +0100poscat(~poscat@user/poscat) poscat
2024-11-08 13:45:06 +0100poscat(~poscat@user/poscat) (Client Quit)
2024-11-08 13:44:16 +0100 <Rembane> Welcome back yin! :/
2024-11-08 13:43:27 +0100 <yin> i thought i got over my hate for record syntax...
2024-11-08 13:43:22 +0100poscat(~poscat@user/poscat) poscat
2024-11-08 13:35:58 +0100 <yin> turns out record update syntax is weirder than i thought https://gitlab.haskell.org/ghc/ghc/-/issues/25456
2024-11-08 13:35:48 +0100poscat0x04(~poscat@user/poscat) (Ping timeout: 276 seconds)