Newest at the top
| 2025-01-30 21:34:50 +0100 | danza | (~danza@user/danza) (Ping timeout: 272 seconds) |
| 2025-01-30 21:34:16 +0100 | weary-traveler | (~user@user/user363627) user363627 |
| 2025-01-30 21:31:57 +0100 | danz96699 | (~danza@user/danza) danza |
| 2025-01-30 21:31:38 +0100 | acidjnk_new3 | (~acidjnk@p200300d6e7283f4644f622875d25c5df.dip0.t-ipconnect.de) (Ping timeout: 245 seconds) |
| 2025-01-30 21:31:10 +0100 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 252 seconds) |
| 2025-01-30 21:28:29 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds) |
| 2025-01-30 21:25:39 +0100 | wootehfoot | (~wootehfoo@user/wootehfoot) (Read error: Connection reset by peer) |
| 2025-01-30 21:18:55 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-01-30 21:09:31 +0100 | ljdarj | (~Thunderbi@user/ljdarj) (Ping timeout: 252 seconds) |
| 2025-01-30 21:08:14 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 272 seconds) |
| 2025-01-30 21:04:44 +0100 | zmt00 | (~zmt00@user/zmt00) (Ping timeout: 260 seconds) |
| 2025-01-30 21:03:33 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-01-30 21:01:21 +0100 | zmt01 | (~zmt00@user/zmt00) zmt00 |
| 2025-01-30 21:00:49 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 248 seconds) |
| 2025-01-30 21:00:41 +0100 | caconym | (~caconym@user/caconym) caconym |
| 2025-01-30 21:00:03 +0100 | caconym | (~caconym@user/caconym) (Quit: bye) |
| 2025-01-30 20:57:51 +0100 | <nitrix> | Normal debugging yes, type debugging no. The more you know, the more tempted you are to use sophisticated types. |
| 2025-01-30 20:56:22 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-01-30 20:56:18 +0100 | danza | (~danza@user/danza) danza |
| 2025-01-30 20:56:02 +0100 | danza | (~danza@user/danza) (Remote host closed the connection) |
| 2025-01-30 20:54:10 +0100 | <euouae> | I'm sure it gets better with practice |
| 2025-01-30 20:54:05 +0100 | <euouae> | right unfortunately there's normal debugging and type debugging when you write haskell |
| 2025-01-30 20:53:40 +0100 | <nitrix> | Type inference is the term you're looking for. |
| 2025-01-30 20:53:38 +0100 | <euouae> | in terms of ... I'm lacking the terms, but whatever the polymorphism and other derivations are |
| 2025-01-30 20:53:23 +0100 | <euouae> | where I'm trying to understand what the type checker is "thinking" |
| 2025-01-30 20:53:09 +0100 | <euouae> | yup, can't use it in the middle of stuff though |
| 2025-01-30 20:52:55 +0100 | <tomsmeding> | euouae: ':t' shows the type of an expression |
| 2025-01-30 20:52:53 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds) |
| 2025-01-30 20:52:43 +0100 | <yahb2> | "hi" :: String |
| 2025-01-30 20:52:43 +0100 | <tomsmeding> | % :t "hi" |
| 2025-01-30 20:52:37 +0100 | <nitrix> | I guess the Num a => a on the other lines gets truncated in the response. |
| 2025-01-30 20:52:33 +0100 | <euouae> | not just lsp stuff in files |
| 2025-01-30 20:52:28 +0100 | <euouae> | yeah because I wanted something for the REPL too |
| 2025-01-30 20:52:22 +0100 | <euouae> | Ah nice tha'ts a cool trick thank you |
| 2025-01-30 20:52:07 +0100 | <lambdabot> | • In the second argument of ‘(++)’, namely ‘_’ |
| 2025-01-30 20:52:07 +0100 | <lambdabot> | • Found hole: _ :: [Char] |
| 2025-01-30 20:52:07 +0100 | <lambdabot> | error: |
| 2025-01-30 20:52:03 +0100 | <tomsmeding> | > "hi" ++ _ |
| 2025-01-30 20:51:56 +0100 | <lambdabot> | Where: ‘a’ is a rigid type variable bound by |
| 2025-01-30 20:51:56 +0100 | <lambdabot> | • Found hole: _ :: a |
| 2025-01-30 20:51:56 +0100 | <lambdabot> | error: |
| 2025-01-30 20:51:51 +0100 | <nitrix> | > 1 + _ |
| 2025-01-30 20:51:41 +0100 | <euouae> | I'll come to that later at some point. Printf debugging is not the best but it is what it is |
| 2025-01-30 20:51:17 +0100 | zmt00 | (~zmt00@user/zmt00) zmt00 |
| 2025-01-30 20:50:59 +0100 | <tomsmeding> | for runtime debugging, the most reliable go-to is still "printf debugging" with Debug.Trace |
| 2025-01-30 20:50:55 +0100 | <nitrix> | Most LSP integrations will tell you that. You can also put a type hole with _ and see what the compiler thinks. |
| 2025-01-30 20:50:33 +0100 | <tomsmeding> | oh for sure, the language server supports type queries |
| 2025-01-30 20:50:19 +0100 | <euouae> | that'd be type debugging |
| 2025-01-30 20:50:17 +0100 | <euouae> | for example is there a way to query what the type checker thinks of an expression in the middle of a big expression? |
| 2025-01-30 20:49:57 +0100 | <euouae> | hm... well. can't have it all. |