Newest at the top
| 2025-06-14 20:27:54 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-14 20:27:53 +0200 | CiaoSen | (~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) CiaoSen |
| 2025-06-14 20:27:32 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-14 20:26:19 +0200 | haritz | (~hrtz@user/haritz) haritz |
| 2025-06-14 20:26:19 +0200 | haritz | (~hrtz@152.37.64.162) (Changing host) |
| 2025-06-14 20:26:19 +0200 | haritz | (~hrtz@152.37.64.162) |
| 2025-06-14 20:19:58 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-14 20:19:34 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-14 20:18:40 +0200 | gmg | (~user@user/gehmehgeh) (Ping timeout: 244 seconds) |
| 2025-06-14 20:12:31 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-14 20:12:08 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-14 20:11:12 +0200 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) (Quit: Leaving...) |
| 2025-06-14 20:09:12 +0200 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) bitdex |
| 2025-06-14 20:03:46 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-14 20:03:22 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-14 19:59:51 +0200 | todi | (~todi@p57803331.dip0.t-ipconnect.de) todi |
| 2025-06-14 19:58:32 +0200 | tmciver | (~tim@syn-198-255-177-240.res.spectrum.com) tmciver |
| 2025-06-14 19:57:41 +0200 | tmciver | (~tim@syn-198-255-177-240.res.spectrum.com) (Ping timeout: 265 seconds) |
| 2025-06-14 19:56:16 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-14 19:56:14 +0200 | <haskellbridge> | <maerwald> https://gitlab.haskell.org/ghc/ghc/-/issues/26067#note_624172 |
| 2025-06-14 19:55:55 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-14 19:55:32 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich |
| 2025-06-14 19:55:13 +0200 | <haskellbridge> | <maerwald> We're going to get GHC LTS releases |
| 2025-06-14 19:55:02 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Quit: peterbecich) |
| 2025-06-14 19:51:22 +0200 | <monochrom> | BTW last time an installer got stuck (and locked up the whole system heh) was KiCS2 (a Curry compiler) and it was just taking up 7GB of memory so my system went into perpetual swapping. |
| 2025-06-14 19:50:04 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-14 19:49:43 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-14 19:47:32 +0200 | <monochrom> | BTW about "old version": If you have watched the Haskell ecosystem for a while, you will realize that latest GHC versions can be buggy, maximum surprise, and incompatible with most libraries. It's why ghcup's recommendation plays wait-and-see. |
| 2025-06-14 19:45:15 +0200 | <monochrom> | The only one time I got a failure from ghcup with default settings/options was just disk full. |
| 2025-06-14 19:42:18 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-14 19:41:55 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-14 19:40:05 +0200 | <humasect> | ghcup stuck, i will just go plainly. |
| 2025-06-14 19:39:18 +0200 | inline | (~inline@ip-005-146-196-202.um05.pools.vodafone-ip.de) Inline |
| 2025-06-14 19:36:21 +0200 | Pozyomka | (~pyon@user/pyon) pyon |
| 2025-06-14 19:35:09 +0200 | segfaultfizzbuzz | (~segfaultf@12.172.219.122) (Ping timeout: 260 seconds) |
| 2025-06-14 19:35:07 +0200 | FANTOM | (~fantom@33be818f.skybroadband.com) (Ping timeout: 244 seconds) |
| 2025-06-14 19:33:09 +0200 | jle` | (~jle`@2603:8001:3b00:11:5d33:cae7:6ac0:fc3b) jle` |
| 2025-06-14 19:32:24 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich |
| 2025-06-14 19:31:46 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-14 19:31:31 +0200 | <humasect> | hmm |
| 2025-06-14 19:31:26 +0200 | <humasect> | it seems one-directional, like flow of time (toward depth also) ; why i mention prolog, can go backwards as well |
| 2025-06-14 19:31:24 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-14 19:29:42 +0200 | iNomad | (~iNomad@user/iNomad) (Quit: leaving) |
| 2025-06-14 19:29:07 +0200 | <segfaultfizzbuzz> | or maybe there are better ways to specify these identities |
| 2025-06-14 19:28:53 +0200 | <segfaultfizzbuzz> | so like "higher arity means much greater difficulty in specifying algebraic identities for functions"... therefore algebraic identites are unnatural, or functions most naturally only combine pairs? i can't tell |
| 2025-06-14 19:27:52 +0200 | <segfaultfizzbuzz> | sure you can do f (a, b, c) -> d if you want, but that is rather less common in fp |
| 2025-06-14 19:27:34 +0200 | prdak1 | prdak |
| 2025-06-14 19:27:34 +0200 | prdak | (~Thunderbi@user/prdak) (Ping timeout: 260 seconds) |
| 2025-06-14 19:27:29 +0200 | <humasect> | tuples...? |
| 2025-06-14 19:27:06 +0200 | <segfaultfizzbuzz> | in other words, it feels like these identities make sense when you only have functions which look like f(a, b) -> c, rather than the more common f a -> b -> c -> d -> e -> z |