Newest at the top
| 2026-03-04 01:29:28 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-03-04 01:27:34 +0100 | <EvanR> | cool I got the type of start in the first try... at least the most general type xD |
| 2026-03-04 01:23:47 +0100 | <lambdabot> | () |
| 2026-03-04 01:23:46 +0100 | <int-e> | @type () -- or this for lambdabot |
| 2026-03-04 01:23:12 +0100 | <yahb2> | () -- the space is required for yahb2; the : is for ghci :: () |
| 2026-03-04 01:23:12 +0100 | <int-e> | % :type () -- the space is required for yahb2; the : is for ghci |
| 2026-03-04 01:22:39 +0100 | chromoblob | tried |
| 2026-03-04 01:22:08 +0100 | <chromoblob> | %type () |
| 2026-03-04 01:19:37 +0100 | <chromoblob> | wow |
| 2026-03-04 01:19:25 +0100 | <int-e> | yin: if you want to go mildly insane, work out the type of the `start` in there. |
| 2026-03-04 01:18:55 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2026-03-04 01:18:37 +0100 | <yin> | int-e: yay continuations |
| 2026-03-04 01:18:27 +0100 | <lambdabot> | * says: | shapr remembers that hours of coding can save minutes of thinking |
| 2026-03-04 01:18:27 +0100 | <int-e> | @quote * |
| 2026-03-04 01:18:11 +0100 | <chromoblob> | int-e: wow |
| 2026-03-04 01:17:19 +0100 | <EvanR> | it's like * in C >:D |
| 2026-03-04 01:17:15 +0100 | <yin> | this is not good |
| 2026-03-04 01:17:01 +0100 | <lambdabot> | [1,2,3] |
| 2026-03-04 01:17:00 +0100 | <yin> | > succ` fmap `[0..2] |
| 2026-03-04 01:16:43 +0100 | <lambdabot> | [1,2] |
| 2026-03-04 01:16:42 +0100 | <yin> | > succ ` fmap ` [0..1] |
| 2026-03-04 01:16:28 +0100 | <yin> | ah, you can leave whitespace between ``..... |
| 2026-03-04 01:15:04 +0100 | <lambdabot> | [6] |
| 2026-03-04 01:15:02 +0100 | <int-e> | > let start c = c []; push z x c = c (x:z); add (x:y:z) c = c (x+y:z); end z = z in start push 1 push 2 push 3 add add end -- who needs infix operators anyway |
| 2026-03-04 01:14:48 +0100 | <chromoblob> | every backtick enters a backtick mode, in it either an id or an opening paren, latter enters a level and we're in non-backtick again; closing paren checks the level and exits into non-backtick on previous level |
| 2026-03-04 01:13:51 +0100 | <geekosaur> | also if it allowed general expressions |
| 2026-03-04 01:13:43 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-03-04 01:13:42 +0100 | <geekosaur> | no, this is if you could |
| 2026-03-04 01:13:34 +0100 | <yin> | no way, you can nest ``? |
| 2026-03-04 01:11:39 +0100 | <geekosaur> | and in Haskell in particular, with its rather finely diced syntax… put soemthing in the wrong place by accident and the error messages would resemble C++ template errors ☺ |
| 2026-03-04 01:11:21 +0100 | Tuplanolla | (~Tuplanoll@88-114-89-88.elisa-laajakaista.fi) Tuplanolla |
| 2026-03-04 01:11:04 +0100 | <chromoblob> | that's why i used parentheses |
| 2026-03-04 01:10:25 +0100 | <geekosaur> | and do remember that code is written to be readable by humans, not the computer. if we cared about the computer reading it we'd still be keying programs in in hex |
| 2026-03-04 01:09:55 +0100 | <geekosaur> | even with escapes it was really hard to deal with; without, well, I'm sure you could get a lexer to handle it but $* help the reader |
| 2026-03-04 01:09:48 +0100 | <yin> | x `w `f` z` y |
| 2026-03-04 01:09:46 +0100 | <EvanR> | "abc "def" ghi" |
| 2026-03-04 01:09:16 +0100 | <geekosaur> | (well, with escapes) |
| 2026-03-04 01:09:08 +0100 | <geekosaur> | because those _did_ nest |
| 2026-03-04 01:08:56 +0100 | <geekosaur> | go look at why the Bourne shell's backrticks were replaced with `$()` |
| 2026-03-04 01:08:54 +0100 | <EvanR> | lol |
| 2026-03-04 01:08:46 +0100 | <EvanR> | imagine if strings could be nested without escaping the " |
| 2026-03-04 01:08:05 +0100 | <chromoblob> | why would it be a nightmare? |
| 2026-03-04 01:08:05 +0100 | <int-e> | x ◖infix◗ y |
| 2026-03-04 01:07:37 +0100 | <yin> | whitespace as application would be great too |
| 2026-03-04 01:06:42 +0100 | <geekosaur> | plan 9 user? 😛 |
| 2026-03-04 01:06:26 +0100 | <yin> | i wish `f` was just 'f or even `f would be fine |
| 2026-03-04 01:06:17 +0100 | <geekosaur> | consider string parsing |
| 2026-03-04 01:06:05 +0100 | <geekosaur> | if they'd chosen a different closing character it would have been easier |
| 2026-03-04 01:05:50 +0100 | <geekosaur> | chromoblob: not gonna happen, nightmare to parse those nested backticks and in general backticked expressions |
| 2026-03-04 01:04:53 +0100 | <lambdabot> | LowercaseLetter |