Newest at the top
2024-04-30 14:19:35 +0200 | kritzefitz | (~kritzefit@debian/kritzefitz) |
2024-04-30 14:18:23 +0200 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) |
2024-04-30 14:17:50 +0200 | cashew | (~cashewsta@65.17.175.150) (Ping timeout: 245 seconds) |
2024-04-30 14:17:10 +0200 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) (Remote host closed the connection) |
2024-04-30 14:16:41 +0200 | yin | (~yin@user/zero) |
2024-04-30 14:16:40 +0200 | kritzefitz | (~kritzefit@debian/kritzefitz) (Ping timeout: 260 seconds) |
2024-04-30 14:12:33 +0200 | cashew | (~cashewsta@65.17.175.150) |
2024-04-30 14:09:57 +0200 | euleritian | (~euleritia@77.22.252.56) |
2024-04-30 14:09:23 +0200 | ddellacosta | (~ddellacos@ool-44c73d29.dyn.optonline.net) (Ping timeout: 268 seconds) |
2024-04-30 14:08:10 +0200 | euleritian | (~euleritia@dynamic-176-006-191-139.176.6.pool.telefonica.de) (Read error: Connection reset by peer) |
2024-04-30 14:01:49 +0200 | zetef | (~quassel@2a02:2f00:5202:1200:2128:605:71c4:66a4) (Ping timeout: 256 seconds) |
2024-04-30 14:01:10 +0200 | <haskellbridge> | <maralorn> Huh, maybe I can just copy the implementation from optics. It seems to go via van Laarhoven lenses anyway. |
2024-04-30 13:59:09 +0200 | <haskellbridge> | <maralorn> Dear Lens experts: Can you please tell me how to implement an indexedAdjoin for indexedtraversals in the lens library? I thought maybe it isn’t possible, but optics has iadjoin and I also see no reason for it to be impossible. |
2024-04-30 13:58:29 +0200 | cashew | (~cashewsta@65.17.175.150) (Ping timeout: 240 seconds) |
2024-04-30 13:54:27 +0200 | zetef | (~quassel@2a02:2f00:5202:1200:2128:605:71c4:66a4) |
2024-04-30 13:46:59 +0200 | cashew | (~cashewsta@65.17.175.150) |
2024-04-30 13:42:13 +0200 | byte | (~byte@149.28.222.189) |
2024-04-30 13:41:41 +0200 | euleritian | (~euleritia@dynamic-176-006-191-139.176.6.pool.telefonica.de) |
2024-04-30 13:41:23 +0200 | euleritian | (~euleritia@77.22.252.56) (Ping timeout: 264 seconds) |
2024-04-30 13:39:35 +0200 | L29Ah | (~L29Ah@wikipedia/L29Ah) |
2024-04-30 13:38:23 +0200 | byte | (~byte@149.28.222.189) (Ping timeout: 264 seconds) |
2024-04-30 13:34:50 +0200 | L29Ah | (~L29Ah@wikipedia/L29Ah) (Quit: Gateway shutdown) |
2024-04-30 13:20:03 +0200 | tromp | (~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…) |
2024-04-30 13:19:38 +0200 | euleritian | (~euleritia@77.22.252.56) |
2024-04-30 13:19:19 +0200 | euleritian | (~euleritia@dynamic-176-006-191-139.176.6.pool.telefonica.de) (Read error: Connection reset by peer) |
2024-04-30 13:18:25 +0200 | cashew | (~cashewsta@65.17.175.150) (Ping timeout: 246 seconds) |
2024-04-30 13:16:21 +0200 | mima | (~mmh@aftr-62-216-211-48.dynamic.mnet-online.de) (Ping timeout: 256 seconds) |
2024-04-30 13:15:04 +0200 | <[exa]> | but other than that good question, I only see cabal specifying the actual data files (like the ones that would get installed and sourced with `getDataFileName` |
2024-04-30 13:12:43 +0200 | <[exa]> | probie: tbh best to have them generated with some program in test/ because it gives others a chance to generate harsher test data |
2024-04-30 13:12:04 +0200 | cashew | (~cashewsta@65.17.175.150) |
2024-04-30 13:10:29 +0200 | euleritian | (~euleritia@dynamic-176-006-191-139.176.6.pool.telefonica.de) |
2024-04-30 13:09:48 +0200 | euleritian | (~euleritia@77.22.252.56) (Ping timeout: 252 seconds) |
2024-04-30 13:09:38 +0200 | tromp | (~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) |
2024-04-30 13:08:49 +0200 | jorj | (~jorj@user/jorj) (Quit: jorj) |
2024-04-30 13:00:53 +0200 | lortabac | (~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4) |
2024-04-30 12:59:55 +0200 | cashew | (~cashewsta@65.17.175.150) (Ping timeout: 260 seconds) |
2024-04-30 12:59:26 +0200 | stiell_ | (~stiell@gateway/tor-sasl/stiell) |
2024-04-30 12:59:08 +0200 | tromp | (~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…) |
2024-04-30 12:59:05 +0200 | demon-cat | (~demon-cat@82-132-225-207.dab.02.net) (Read error: Connection reset by peer) |
2024-04-30 12:58:10 +0200 | stiell_ | (~stiell@gateway/tor-sasl/stiell) (Ping timeout: 260 seconds) |
2024-04-30 12:54:57 +0200 | cashew | (~cashewsta@65.17.175.150) |
2024-04-30 12:53:31 +0200 | Lord_of_Life_ | Lord_of_Life |
2024-04-30 12:51:10 +0200 | Lord_of_Life | (~Lord@user/lord-of-life/x-2819915) (Ping timeout: 255 seconds) |
2024-04-30 12:50:35 +0200 | Lord_of_Life_ | (~Lord@user/lord-of-life/x-2819915) |
2024-04-30 12:49:52 +0200 | cashew | (~cashewsta@65.17.175.150) (Ping timeout: 260 seconds) |
2024-04-30 12:48:26 +0200 | Square3 | (~Square4@user/square) |
2024-04-30 12:43:21 +0200 | cashew | (~cashewsta@65.17.175.150) |
2024-04-30 12:41:55 +0200 | <probie> | Does anyone have strong opinions where test data should go? Should it go under /test and coexist with source files, or should it live somewhere else? |
2024-04-30 12:38:16 +0200 | kritzefitz | (~kritzefit@debian/kritzefitz) |
2024-04-30 12:26:59 +0200 | kritzefitz | (~kritzefit@debian/kritzefitz) (Ping timeout: 264 seconds) |