Newest at the top
| 2025-06-03 18:34:59 +0200 | trickard | (~trickard@cpe-51-98-47-163.wireline.com.au) |
| 2025-06-03 18:33:34 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-03 18:33:08 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-03 18:28:52 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-03 18:28:29 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-03 18:25:33 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-03 18:25:07 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-03 18:22:01 +0200 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 252 seconds) |
| 2025-06-03 18:21:49 +0200 | merijn | (~merijn@77.242.116.146) (Ping timeout: 260 seconds) |
| 2025-06-03 18:21:27 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-03 18:21:04 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-03 18:19:59 +0200 | sawilagar | (~sawilagar@user/sawilagar) sawilagar |
| 2025-06-03 18:16:49 +0200 | manwithluck | (~manwithlu@2a09:bac5:5082:2432::39b:b0) manwithluck |
| 2025-06-03 18:16:15 +0200 | <EvanR> | but noooooo we can't return two values |
| 2025-06-03 18:16:12 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-03 18:15:59 +0200 | <EvanR> | and returning two values would solve the lack of pattern matching or deconstructive assignment |
| 2025-06-03 18:15:51 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-03 18:15:34 +0200 | <EvanR> | all you need is pair, it could even be a primitive |
| 2025-06-03 18:10:27 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-03 18:10:12 +0200 | kuribas | (~user@ip-188-118-57-242.reverse.destiny.be) (Quit: ERC 5.5.0.29.1 (IRC client for GNU Emacs 29.3)) |
| 2025-06-03 18:10:05 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-03 18:05:29 +0200 | <haskellbridge> | <Morj> Yeah, and I'm not sure if turing incompleteness is what I want |
| 2025-06-03 18:05:29 +0200 | <haskellbridge> | <Morj> Why not omit Nil? And for some swag #define , :* |
| 2025-06-03 18:05:29 +0200 | <haskellbridge> | <Morj> Rust and C++ on the other hand |
| 2025-06-03 18:05:27 +0200 | <haskellbridge> | <Morj> Ironically I don't really feel this problem in haskell, because I rarely need to be generic over tuple size, except with Generics |
| 2025-06-03 18:05:27 +0200 | <haskellbridge> | <Morj> You would then represent functions as accepting a tuple, and have variadics for free |
| 2025-06-03 18:05:25 +0200 | <haskellbridge> | <Morj> The more I live the more I believe that inductive tuples are a better solution, especially for C-inspired languages |
| 2025-06-03 18:05:07 +0200 | <dminuoso> | https://cabal.readthedocs.io/en/3.4/cabal-project.html#cfg-field-flags |
| 2025-06-03 18:04:28 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-03 18:04:07 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-03 18:04:04 +0200 | <dminuoso> | You can definitely put flags in a cabal project |
| 2025-06-03 18:03:24 +0200 | AlexNoo | (~AlexNoo@178.34.162.18) (Quit: Leaving) |
| 2025-06-03 18:02:33 +0200 | trickard | (~trickard@cpe-51-98-47-163.wireline.com.au) (Read error: Connection reset by peer) |
| 2025-06-03 18:02:29 +0200 | AlexZenon | (~alzenon@178.34.162.18) (Quit: ;-) |
| 2025-06-03 17:59:10 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-03 17:58:47 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-03 17:56:04 +0200 | <dolio> | No, doesn't seem like you can put flags in a cabal.project. |
| 2025-06-03 17:55:22 +0200 | <yahb2> | "gmp" |
| 2025-06-03 17:55:22 +0200 | <EvanR> | % backendName |
| 2025-06-03 17:55:16 +0200 | <yahb2> | <no output> |
| 2025-06-03 17:55:15 +0200 | <EvanR> | % import GHC.Num.Backend (backendName) |
| 2025-06-03 17:53:20 +0200 | <dolio> | Which isn't cabal based. |
| 2025-06-03 17:52:47 +0200 | <dolio> | Yeah, I wasn't sure if you could put flags in a cabal.project. And I the -Werror isn't in the .cabal files. I add it in my cabal.project to match whatever the CI is doing. |
| 2025-06-03 17:51:49 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-03 17:51:44 +0200 | <geekosaur> | hm, except I don't know if the flag() condition works in the latter |
| 2025-06-03 17:51:27 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-03 17:51:17 +0200 | <geekosaur> | no, that's what hellwolf wants to avoid. you put that in cabal files, or if you can't modify those directlyu then package stanzas in cabal.project |
| 2025-06-03 17:50:02 +0200 | <dolio> | You put that in your cabal.project? |
| 2025-06-03 17:49:27 +0200 | <geekosaur> | alternately reverse the default so CI runs with -fwerror |
| 2025-06-03 17:48:11 +0200 | <geekosaur> | (re -Werror) |