Newest at the top
| 2025-12-01 21:17:14 +0100 | <chromoblob> | >:( |
| 2025-12-01 21:15:46 +0100 | <tomsmeding> | it's best-effort anyway |
| 2025-12-01 21:15:36 +0100 | <tomsmeding> | and probably impossible |
| 2025-12-01 21:15:30 +0100 | <tomsmeding> | which I do _not_ want to do because that's a hell of a job |
| 2025-12-01 21:15:24 +0100 | <tomsmeding> | also, if I'd be listed, I would feel the responsibility to make sure that the syntax file is actually correct |
| 2025-12-01 21:14:56 +0100 | <tomsmeding> | people who write fmap ` fmap ` fmap can just do that in some other editor |
| 2025-12-01 21:14:45 +0100 | <tomsmeding> | if I was, I'm not sure I would have passed that change |
| 2025-12-01 21:14:37 +0100 | <tomsmeding> | like, yes I use vim heavily and I write lots of haskell, but no I would not particularly like to be listed as maintainer of the haskell syntax file lol |
| 2025-12-01 21:14:08 +0100 | <[exa]> | tomsmeding: anyway yeah that PR was full of surprise |
| 2025-12-01 21:13:49 +0100 | <EvanR> | also that |
| 2025-12-01 21:13:45 +0100 | <tomsmeding> | EvanR: no it's because the notation is bad |
| 2025-12-01 21:13:40 +0100 | <EvanR> | it's like... x and y |
| 2025-12-01 21:13:33 +0100 | <EvanR> | that they never actually write concrete examples is why it's hard to remember |
| 2025-12-01 21:13:32 +0100 | <tomsmeding> | oh right |
| 2025-12-01 21:13:14 +0100 | <[exa]> | yes, [blab-las+dweur*yiwuerywer/y] looks unhappy |
| 2025-12-01 21:12:46 +0100 | <tomsmeding> | if the term to replace is long, you mean? |
| 2025-12-01 21:12:43 +0100 | <[exa]> | (probably not a concern for symbolic logic papers tho) |
| 2025-12-01 21:12:26 +0100 | <[exa]> | tomsmeding: isn't that quite inconvenient to read if your replacement is a long term |
| 2025-12-01 21:12:18 +0100 | <tomsmeding> | I read it as "E with x for y" |
| 2025-12-01 21:11:51 +0100 | spew | (~spew@user/spew) (Quit: spew) |
| 2025-12-01 21:11:29 +0100 | <tomsmeding> | and authors that use it the other way round should just be shooed back to their writing desk and replace / with := |
| 2025-12-01 21:11:20 +0100 | <monochrom> | [x/y/g] >:) |
| 2025-12-01 21:11:01 +0100 | <tomsmeding> | yes I'm not saying it's good notation or that the mnemonic is perfect, but it works for me :p |
| 2025-12-01 21:10:55 +0100 | <EvanR> | well 4 is not prime |
| 2025-12-01 21:10:28 +0100 | <[exa]> | EvanR: [goedel voice:] ofcourse it's a string of multiplied primes! |
| 2025-12-01 21:10:20 +0100 | <tomsmeding> | lol! |
| 2025-12-01 21:10:18 +0100 | <tomsmeding> | > The header of the syntax file lists the Haskell-Cafe ML as the maintainer. This is so unusual for a distributed syntax file that it might be the only example. |
| 2025-12-01 21:10:11 +0100 | <mauke> | the correct syntax should be ${foo/x/y} |
| 2025-12-01 21:10:06 +0100 | <EvanR> | at most one each |
| 2025-12-01 21:10:02 +0100 | <[exa]> | but aaaaaaaaaaaaaa |
| 2025-12-01 21:10:00 +0100 | <[exa]> | I'm grateful for the mnemonic |
| 2025-12-01 21:09:59 +0100 | <EvanR> | maybe if you insist that it's a string of multiplied primes |
| 2025-12-01 21:09:45 +0100 | <chromoblob> | i made that mnemonic too, but then i saw [x/y] defined to mean the opposite, replace x with y |
| 2025-12-01 21:09:32 +0100 | <EvanR> | lol |
| 2025-12-01 21:09:22 +0100 | <mauke> | tomsmeding: yeah, that's just (morally) wrong |
| 2025-12-01 21:09:06 +0100 | kuribas | (~user@2a02-1810-2825-6000-91ce-6f5d-5219-16e3.ip6.access.telenet.be) (Remote host closed the connection) |
| 2025-12-01 21:08:37 +0100 | <tomsmeding> | it doesn't quite work because it replaces _all_ occurrences, not just one |
| 2025-12-01 21:08:21 +0100 | <tomsmeding> | EvanR [exa]: the way I remember the meaning of [x/y] is "multiply by x, then divide by y"; if you have 2*3*4*5 and you do *17/5 you replace the 5 with 17, so E[x/y] means replace y with x |
| 2025-12-01 21:07:50 +0100 | <[exa]> | oh I wish editors had proper support for hiding these (and popping them out) |
| 2025-12-01 21:07:26 +0100 | <mauke> | that's one of the more interesting wrinkles I know of that are in real use |
| 2025-12-01 21:05:20 +0100 | <monochrom> | No. |
| 2025-12-01 21:05:07 +0100 | <monochrom> | Python does not allow <exprBool> to be its own "if-else" but it is easy to see there would be no ambiguity, so I allow it in my homework! |
| 2025-12-01 21:04:51 +0100 | <mauke> | monochrom: have you already done here-docs? |
| 2025-12-01 21:04:27 +0100 | iqubic | (~sophia@2601:602:9203:1660:c137:59bd:3f5b:b4a7) (Remote host closed the connection) |
| 2025-12-01 21:04:08 +0100 | trickard_ | (~trickard@cpe-85-98-47-163.wireline.com.au) |
| 2025-12-01 21:03:55 +0100 | trickard | (~trickard@cpe-85-98-47-163.wireline.com.au) (Read error: Connection reset by peer) |
| 2025-12-01 21:03:45 +0100 | <monochrom> | Last time I was very inspired by Python "<expr1> if <exprBool> else <expr0>". (I was primed; I was first inspired by Hoare's "<expr1> ◁ <exprBool> ▷ <expr0>".) |
| 2025-12-01 21:03:29 +0100 | <[exa]> | and then you read a paper and they do [x\y] to disambiguate for good |
| 2025-12-01 21:03:18 +0100 | ljdarj | (~Thunderbi@user/ljdarj) ljdarj |
| 2025-12-01 21:03:12 +0100 | <chromoblob> | me too |