Newest at the top
| 2025-03-28 07:45:13 +0100 | Digit | (~user@user/digit) (Ping timeout: 252 seconds) |
| 2025-03-28 07:43:59 +0100 | Digitteknohippie | (~user@user/digit) Digit |
| 2025-03-28 07:43:55 +0100 | echoreply | (~echoreply@45.32.163.16) echoreply |
| 2025-03-28 07:43:22 +0100 | echoreply | (~echoreply@2001:19f0:9002:1f3b:5400:ff:fe6f:8b8d) (Quit: WeeChat 2.8) |
| 2025-03-28 07:41:00 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds) |
| 2025-03-28 07:35:57 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-03-28 07:34:57 +0100 | aetepe | (~aetepe@188.119.58.34) (Ping timeout: 248 seconds) |
| 2025-03-28 07:33:50 +0100 | <Leary> | ski: I see. Those tail calls and algebraicity are probably related. |
| 2025-03-28 07:31:40 +0100 | hattckory | (~hattckory@70.27.118.207) |
| 2025-03-28 07:30:53 +0100 | <Leary> | ed `try` disguised as `catch`: `M a -> M (Either E a)` ~ `M a -> Codensity M (Either E a)` ~ `M a -> (Either E a -> M b) -> M b` ~ `Sig_Try (M b) -> M b` where `Sig_Try r = (M a, Either E a -> r)`. |
| 2025-03-28 07:30:52 +0100 | <Leary> | thirdofmay: I might be beating a dead horse at this point, but there are some details I kinda bungled due to algebraicity depending on precisely how on operation is expressed (and I prefer to fix these things). `catch :: M a -> (E -> M a) -> M a` naively becomes `catch :: Sig_Catch (M a) -> M a` with `Sig_Catch r = (r, E -> r)` which /isn't/ algebraic, but the last `data Catch` I wrote has a `runCatch` that actually /is/. That's because I cheated and us |
| 2025-03-28 07:30:14 +0100 | aetepe | (~aetepe@188.119.58.34) aetepe |
| 2025-03-28 07:24:49 +0100 | hattckory | (~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca) (Ping timeout: 248 seconds) |
| 2025-03-28 07:24:46 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds) |
| 2025-03-28 07:23:49 +0100 | <sim590> | Ah. I get it. The second version doesn't take into account repeating numbers while the Set approach took care of that. |
| 2025-03-28 07:22:51 +0100 | emmanuelux_ | (~emmanuelu@user/emmanuelux) (Read error: Connection reset by peer) |
| 2025-03-28 07:20:57 +0100 | <sim590> | The funny thing is with the first function, the algorithm executes in 280 seconds while with the second function, it executes in 420 seconds... (it's by now means optimal, I tried a brute force approach with the help of an upper bound) |
| 2025-03-28 07:20:34 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-03-28 07:19:09 +0100 | LainExperiments | (~LainExper@user/LainExperiments) LainExperiments |
| 2025-03-28 07:17:23 +0100 | rvalue | (~rvalue@user/rvalue) rvalue |
| 2025-03-28 07:16:51 +0100 | rvalue | (~rvalue@user/rvalue) (Read error: Connection reset by peer) |
| 2025-03-28 07:12:49 +0100 | <sim590> | To me, I thought that the second version made more sense... I'm now doubting if I accidently got the right answer because of a bad upper bound and a bad algorithm... lol |
| 2025-03-28 07:10:34 +0100 | <sim590> | it simpler. I rewrote it to https://paste.debian.net/1365805/. I don't understand why, but now my whole algorithme doesn't give me the right answer anymore. |
| 2025-03-28 07:10:32 +0100 | <sim590> | Consider the following problem: https://projecteuler.net/problem=32. Which I have solved. My algorithm uses some math analysis to determine an upper bound for the search space. Anyway, I use the following function to recognize a pandigital triplet: https://paste.debian.net/1365804/. Using this function, my algorithms gave me the right answer. Then, I decided to rewrite the function a bit to make |
| 2025-03-28 07:10:06 +0100 | LainExperiments | (~LainExper@user/LainExperiments) (Ping timeout: 240 seconds) |
| 2025-03-28 07:09:40 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2025-03-28 07:05:47 +0100 | nvoid | (~nvoid@2601:140:8700:25fe:5820:136c:b0ce:f5b1) (Quit: nvoid) |
| 2025-03-28 07:04:46 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-03-28 06:59:40 +0100 | <ski> | one reason being tail calls |
| 2025-03-28 06:59:07 +0100 | <ski> | basically argues for (in Haskell terms) `catchBind :: Exception e => IO a -> (e -> IO b) -> (a -> IO b) -> IO b' being more appropriate as a primitive, than `catch :: Exception e => IO a -> (e -> IO a) -> IO a' |
| 2025-03-28 06:58:19 +0100 | nvoid | (~nvoid@2601:140:8700:25fe:5820:136c:b0ce:f5b1) |
| 2025-03-28 06:58:01 +0100 | <ski> | Leary : "Exceptional Syntax" by Nick Benton,Andrew Kennedy in 2001 at <https://www.microsoft.com/en-us/research/wp-content/uploads/2016/02/exceptionalsyntax.pdf> (<http://lambda-the-ultimate.org/node/1193) |
| 2025-03-28 06:57:19 +0100 | weary-traveler | (~user@user/user363627) (Remote host closed the connection) |
| 2025-03-28 06:57:08 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds) |
| 2025-03-28 06:53:14 +0100 | Square | (~Square@user/square) Square |
| 2025-03-28 06:51:54 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-03-28 06:46:09 +0100 | takuan | (~takuan@d8D86B601.access.telenet.be) |
| 2025-03-28 06:46:08 +0100 | ChaiTRex | (~ChaiTRex@user/chaitrex) ChaiTRex |
| 2025-03-28 06:44:35 +0100 | ChaiTRex | (~ChaiTRex@user/chaitrex) (Remote host closed the connection) |
| 2025-03-28 06:41:03 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2025-03-28 06:36:40 +0100 | Digitteknohippie | Digit |
| 2025-03-28 06:35:20 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-03-28 06:34:13 +0100 | Digit | (~user@user/digit) (Ping timeout: 268 seconds) |
| 2025-03-28 06:33:37 +0100 | aetepe | (~aetepe@188.119.58.34) (Ping timeout: 244 seconds) |
| 2025-03-28 06:33:06 +0100 | <Leary> | ski: I'm not familiar with the paper. I pulled that `data Catch` out of my arse, though it may have been inspired by 'A Framework for Higher-Order Effects & Handlers'. |
| 2025-03-28 06:32:48 +0100 | Digitteknohippie | (~user@user/digit) Digit |
| 2025-03-28 06:29:09 +0100 | aetepe | (~aetepe@188.119.58.34) aetepe |
| 2025-03-28 06:27:19 +0100 | <ski> | mhm |
| 2025-03-28 06:24:34 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds) |
| 2025-03-28 06:24:07 +0100 | <EvanR> | memory management, or lack there of |