Newest at the top
| 2025-04-24 11:11:05 +0200 | <haskellbridge> | <Liamzee> https://hackage.haskell.org/package/resourcet |
| 2025-04-24 11:11:03 +0200 | <haskellbridge> | <Liamzee> and that idea essentially points to ResourceT |
| 2025-04-24 11:10:25 +0200 | <tomsmeding> | it depends on whether the operations you want to perform on that resource are anything like those that are natural on a mutable reference |
| 2025-04-24 11:09:49 +0200 | <haskellbridge> | <Liamzee> beyond, say, the base case of shared memory, does representing network, database, or even file resources as a reference have any advantages at all? |
| 2025-04-24 11:09:18 +0200 | <haskellbridge> | <Liamzee> like, fooRef implies an immutable pointer to a mutable object |
| 2025-04-24 11:08:44 +0200 | <haskellbridge> | <Liamzee> i'm actually wondering if PGRef would offer any advantages over existing systems |
| 2025-04-24 11:04:18 +0200 | chele | (~chele@user/chele) chele |
| 2025-04-24 11:03:59 +0200 | dhil | (~dhil@5.151.29.137) dhil |
| 2025-04-24 11:03:20 +0200 | <tomsmeding> | I'm not sure how that would be more natural using something like a PGRef |
| 2025-04-24 11:03:06 +0200 | <tomsmeding> | Liamzee: core to the API of databases is queries spanning multiple tables and transactions spanning multiple queries |
| 2025-04-24 11:02:54 +0200 | alecs | (~alecs@nat16.software.imdea.org) (Ping timeout: 240 seconds) |
| 2025-04-24 11:00:39 +0200 | <mari-estel> | main drawback i can think of, you lose abstraction over the database engine |
| 2025-04-24 10:59:28 +0200 | <haskellbridge> | <Liamzee> i'm just wondering if PGRef would be a better way to do it than existing systems |
| 2025-04-24 10:59:11 +0200 | <haskellbridge> | <Liamzee> i am |
| 2025-04-24 10:57:49 +0200 | <mari-estel> | are you not using a library Liamzee? |
| 2025-04-24 10:56:29 +0200 | <haskellbridge> | <Liamzee> I mean, afaik, the ecosystem around postgres is relatively mature, but is there a benefit to having a PGRef type? |
| 2025-04-24 10:55:53 +0200 | <haskellbridge> | <Liamzee> that's to say, a Postgres table is described as an immutable reference to a mutable Postgres table in some database |
| 2025-04-24 10:55:10 +0200 | <haskellbridge> | <Liamzee> what are the pros and cons of having a PGRef type? Wherein PG refers to Postgres? |
| 2025-04-24 10:48:01 +0200 | todi | (~todi@p57803331.dip0.t-ipconnect.de) todi |
| 2025-04-24 10:45:24 +0200 | zmt01 | (~zmt00@user/zmt00) (Ping timeout: 245 seconds) |
| 2025-04-24 10:42:15 +0200 | swamp_ | (~zmt00@user/zmt00) zmt00 |
| 2025-04-24 10:40:06 +0200 | econo_ | (uid147250@id-147250.tinside.irccloud.com) (Quit: Connection closed for inactivity) |
| 2025-04-24 10:37:21 +0200 | Square2 | (~Square4@user/square) Square |
| 2025-04-24 10:34:39 +0200 | fp | (~Thunderbi@wireless-86-50-140-117.open.aalto.fi) (Ping timeout: 244 seconds) |
| 2025-04-24 10:32:10 +0200 | superbil | (~superbil@114-32-231-70.hinet-ip.hinet.net) superbil |
| 2025-04-24 10:21:09 +0200 | superbil | (~superbil@114-32-231-70.hinet-ip.hinet.net) (Quit: WeeChat 4.5.2) |
| 2025-04-24 10:18:10 +0200 | prdak | (~Thunderbi@user/prdak) (Quit: prdak) |
| 2025-04-24 10:17:04 +0200 | lisbeths | (uid135845@id-135845.lymington.irccloud.com) lisbeths |
| 2025-04-24 10:03:45 +0200 | notdabs | (~Owner@2600:1700:69cf:9000:c9c8:e2be:ff6d:9e09) (Quit: Leaving) |
| 2025-04-24 10:01:15 +0200 | merijn | (~merijn@77.242.116.146) merijn |
| 2025-04-24 09:58:56 +0200 | tzh | (~tzh@c-76-115-131-146.hsd1.or.comcast.net) (Quit: zzz) |
| 2025-04-24 09:54:57 +0200 | tessier | (~tessier@ec2-184-72-149-67.compute-1.amazonaws.com) (Ping timeout: 248 seconds) |
| 2025-04-24 09:41:09 +0200 | nadja | (~dequbed@banana-new.kilobyte22.de) dequbed |
| 2025-04-24 09:40:57 +0200 | nadja | (~dequbed@banana-new.kilobyte22.de) (Quit: bye!) |
| 2025-04-24 09:39:37 +0200 | machinedgod | (~machinedg@d108-173-18-100.abhsia.telus.net) machinedgod |
| 2025-04-24 09:35:17 +0200 | emmanuelux | (~emmanuelu@user/emmanuelux) (Quit: au revoir) |
| 2025-04-24 09:33:39 +0200 | mari-estel | (~mari-este@user/mari-estel) mari-estel |
| 2025-04-24 09:27:08 +0200 | haritzondo | (~hrtz@152.37.68.178) (Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in) |
| 2025-04-24 09:26:14 +0200 | prdak | (~Thunderbi@user/prdak) prdak |
| 2025-04-24 09:25:31 +0200 | fp | (~Thunderbi@wireless-86-50-140-117.open.aalto.fi) fp |
| 2025-04-24 09:24:47 +0200 | fp | (~Thunderbi@wireless-86-50-140-117.open.aalto.fi) (Ping timeout: 272 seconds) |
| 2025-04-24 09:23:28 +0200 | Sgeo_ | (~Sgeo@user/sgeo) (Read error: Connection reset by peer) |
| 2025-04-24 09:23:01 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds) |
| 2025-04-24 09:22:22 +0200 | alecs | (~alecs@nat16.software.imdea.org) alecs |
| 2025-04-24 09:22:01 +0200 | Lord_of_Life_ | Lord_of_Life |
| 2025-04-24 09:21:24 +0200 | Lord_of_Life | (~Lord@user/lord-of-life/x-2819915) (Ping timeout: 252 seconds) |
| 2025-04-24 09:20:39 +0200 | prdak | (~Thunderbi@user/prdak) (Read error: Connection reset by peer) |
| 2025-04-24 09:20:37 +0200 | Lord_of_Life_ | (~Lord@user/lord-of-life/x-2819915) Lord_of_Life |
| 2025-04-24 09:18:21 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-04-24 09:14:59 +0200 | tromp | (~textual@2001:1c00:3487:1b00:c44:d27d:c88:929f) |