Newest at the top
2024-11-19 11:19:23 +0100 | <Leary> | (where `type f ! k = forall t. f (k @ t)`) |
2024-11-19 11:18:31 +0100 | <Leary> | jackdk: For e.g. `type data Wibble = Wobble Foo | Nibble Wibble Wibble` I'm writing TH that ought to generate `deriving instance Show (Wibble @ t)` given that we already have `Show! Foo` in scope, but really it will generate `deriving instance (Show! Foo, Show! Wibble, Show! Wibble) => Show (Wibble @ t)`. |
2024-11-19 11:13:12 +0100 | <jackdk> | Something like that. I don't know enough about your problem to be sure |
2024-11-19 11:12:58 +0100 | lxsameer | (~lxsameer@Serene/lxsameer) lxsameer |
2024-11-19 11:07:21 +0100 | Guest4 | (~Guest4@102.91.71.26) (Client Quit) |
2024-11-19 11:07:15 +0100 | Guest4 | (~Guest4@102.91.71.26) |
2024-11-19 11:06:41 +0100 | CrunchyFlakes | (~CrunchyFl@ip1f13e94e.dynamic.kabel-deutschland.de) |
2024-11-19 11:06:35 +0100 | mari-estel | (~mari-este@user/mari-estel) mari-estel |
2024-11-19 11:06:05 +0100 | Guest4 | (~Guest4@102.91.71.26) (Client Quit) |
2024-11-19 11:05:43 +0100 | Guest4 | (~Guest4@102.91.71.26) |
2024-11-19 11:02:09 +0100 | <Leary> | jackdk: Hmmm. So the idea is to hide the messy instances by tying them to a private newtype wrapper, then produce a standalone `deriving instance ... via ...` declaration, for which GHC would infer a clean context? Sounds feasible... |
2024-11-19 10:58:11 +0100 | sand-witch | (~m-mzmz6l@vmi833741.contaboserver.net) (Ping timeout: 255 seconds) |
2024-11-19 10:55:54 +0100 | carbolymer | (~carbolyme@dropacid.net) (Read error: Connection reset by peer) |
2024-11-19 10:55:35 +0100 | <jackdk> | Generate deriving via instances instead of generating the constraint directly, maybe? |
2024-11-19 10:54:11 +0100 | Guest4 | (~Guest4@105.112.117.167) (Quit: Ping timeout (120 seconds)) |
2024-11-19 10:53:34 +0100 | L29Ah | (~L29Ah@wikipedia/L29Ah) L29Ah |
2024-11-19 10:44:28 +0100 | Guest4 | (~Guest4@105.112.117.167) |
2024-11-19 10:42:28 +0100 | igemnace | (~igemnace@user/igemnace) igemnace |
2024-11-19 10:41:18 +0100 | sroso | (~sroso@user/SrOso) SrOso |
2024-11-19 10:41:00 +0100 | igemnace | (~igemnace@user/igemnace) (Quit: ZNC 1.9.0+deb2build3 - https://znc.in) |
2024-11-19 10:37:15 +0100 | shilowon | (~Guest4@105.112.117.167) (Quit: Ping timeout (120 seconds)) |
2024-11-19 10:35:37 +0100 | kuribas | (~user@ip-188-118-57-242.reverse.destiny.be) |
2024-11-19 10:25:26 +0100 | vanishingideal | (~vanishing@user/vanishingideal) vanishingideal |
2024-11-19 10:23:37 +0100 | misterfish | (~misterfis@31-161-39-137.biz.kpn.net) misterfish |
2024-11-19 10:17:26 +0100 | <Leary> | So I'm generating instances with TH, but I'm not sure how best to deal with messy constraints. I can generate a /sufficient/ (highly redundant and simplifiable) constraint easily, but cleaning it up looks to be quite a hassle. Any tips? |
2024-11-19 10:14:29 +0100 | misterfish | (~misterfis@h239071.upc-h.chello.nl) (Ping timeout: 248 seconds) |
2024-11-19 10:13:05 +0100 | ash3en | (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) ash3en |
2024-11-19 10:09:25 +0100 | divya | (~user@139.5.11.231) (Read error: Connection reset by peer) |
2024-11-19 10:08:47 +0100 | divya` | (~user@139.5.11.231) |
2024-11-19 10:06:36 +0100 | euleritian | (~euleritia@ip4d16fc9f.dynamic.kabel-deutschland.de) |
2024-11-19 10:06:19 +0100 | euleritian | (~euleritia@dynamic-176-006-146-018.176.6.pool.telefonica.de) (Read error: Connection reset by peer) |
2024-11-19 10:04:47 +0100 | gorignak | (~gorignak@user/gorignak) gorignak |
2024-11-19 10:04:25 +0100 | gorignak | (~gorignak@user/gorignak) (Read error: Connection reset by peer) |
2024-11-19 10:04:21 +0100 | shilowon | (~Guest4@105.112.117.167) |
2024-11-19 10:03:54 +0100 | chele | (~chele@user/chele) chele |
2024-11-19 09:59:00 +0100 | ubert | (~Thunderbi@178.115.41.15.wireless.dyn.drei.com) ubert |
2024-11-19 09:58:19 +0100 | machinedgod | (~machinedg@d108-173-18-100.abhsia.telus.net) machinedgod |
2024-11-19 09:54:57 +0100 | housemate | (~housemate@2a04:9dc0:0:162::5d91:d7ed) (Remote host closed the connection) |
2024-11-19 09:54:20 +0100 | housemate | (~housemate@2a04:9dc0:0:162::5d91:d7ed) housemate |
2024-11-19 09:52:16 +0100 | ski | (~ski@remote11.chalmers.se) (Read error: Connection reset by peer) |
2024-11-19 09:52:02 +0100 | ft | (~ft@p4fc2a26f.dip0.t-ipconnect.de) (Quit: leaving) |
2024-11-19 09:47:21 +0100 | euleritian | (~euleritia@dynamic-176-006-146-018.176.6.pool.telefonica.de) |
2024-11-19 09:46:39 +0100 | euleritian | (~euleritia@77.22.252.159) (Ping timeout: 252 seconds) |
2024-11-19 09:37:45 +0100 | emmanuelux_ | (~emmanuelu@user/emmanuelux) (Quit: au revoir) |
2024-11-19 09:36:55 +0100 | petrichor | (~znc-user@user/petrichor) petrichor |
2024-11-19 09:33:06 +0100 | sawilagar | (~sawilagar@user/sawilagar) sawilagar |
2024-11-19 09:32:36 +0100 | rootnode` | (~user@softbank126206228003.bbtec.net) (Client Quit) |
2024-11-19 09:32:24 +0100 | rootnode` | (~user@softbank126206228003.bbtec.net) |
2024-11-19 09:31:35 +0100 | p3n | (~p3n@2a00:19a0:3:7c:0:d9c6:7cf6:1) p3n |
2024-11-19 09:31:15 +0100 | euleritian | (~euleritia@77.22.252.159) |