Newest at the top
| 2025-11-19 16:27:08 +0100 | tromp | (~textual@2001:1c00:3487:1b00:8d4:6354:928b:6095) (Quit: My iMac has gone to sleep. ZZZzzz…) |
| 2025-11-19 16:18:07 +0100 | merijn | (~merijn@77.242.116.146) merijn |
| 2025-11-19 16:17:04 +0100 | spew | (~spew@user/spew) (Quit: WeeChat 4.6.3) |
| 2025-11-19 16:16:39 +0100 | pr1sm | (~pr1sm@2600:1000:b16f:9264:f8ae:817d:7595:2bb4) |
| 2025-11-19 16:08:53 +0100 | merijn | (~merijn@77.242.116.146) (Ping timeout: 244 seconds) |
| 2025-11-19 16:01:40 +0100 | bggd | (~bgg@2a01:e0a:819:1510:5811:6b25:6842:9300) |
| 2025-11-19 15:52:12 +0100 | <int-e> | (I misspoke, that's just what the code looks like; I'm not reconstructing why that works) |
| 2025-11-19 15:51:29 +0100 | <lucabtz> | i was reading on the wikipedia page about Yoneda's lemma it is related to continuation style programming. someone has a resource on this |
| 2025-11-19 15:51:18 +0100 | <tomsmeding> | getting precise enough definitions that you can even reason about them properly is hard enough, and I'm not even sure I have the proper ones |
| 2025-11-19 15:51:17 +0100 | <int-e> | How did the weird counter work... *twiddle*, ah, this: ``ci`.*`cr (prints lines with 0 stars, 1 stars, 2 stars etc.) |
| 2025-11-19 15:50:38 +0100 | <tomsmeding> | my brain is too fried |
| 2025-11-19 15:50:30 +0100 | <tomsmeding> | noone in the class is going to understand it anyway |
| 2025-11-19 15:50:22 +0100 | <tomsmeding> | I think I'm just going to give up |
| 2025-11-19 15:50:18 +0100 | <tomsmeding> | I've been trying to decide what the stronger-than lattice is between starvation-free, deadlock-free, non-blocking, obstruction-free, lock-free, wait-free is for a lecture I'm giving tomorrow |
| 2025-11-19 15:49:41 +0100 | tomsmeding | was halfway through deciphering what that means and gave up |
| 2025-11-19 15:49:06 +0100 | <int-e> | (weird non-constant memory infinite loop with continuations) |
| 2025-11-19 15:48:44 +0100 | vanishingideal | (~vanishing@user/vanishingideal) (Ping timeout: 244 seconds) |
| 2025-11-19 15:48:24 +0100 | <int-e> | tomsmeding: ``ci`ci |
| 2025-11-19 15:48:07 +0100 | tomsmeding | . o O ( https://en.wikipedia.org/wiki/Unlambda ) |
| 2025-11-19 15:47:53 +0100 | <lambdabot> | 42 |
| 2025-11-19 15:47:51 +0100 | <tomsmeding> | > id`id`id`id`id`id`42 |
| 2025-11-19 15:47:37 +0100 | <int-e> | (TIL, and eww) |
| 2025-11-19 15:47:26 +0100 | <tomsmeding> | or having no spaces around :: |
| 2025-11-19 15:47:25 +0100 | <lambdabot> | 42 |
| 2025-11-19 15:47:24 +0100 | <int-e> | > id ` id ` id ` id ` id ` id ` 42 |
| 2025-11-19 15:46:34 +0100 | <tomsmeding> | vim's haskell highlighter also disregards the possibility of separating type signatures from the definition |
| 2025-11-19 15:46:10 +0100 | <chromoblob> | but it's irritating to have the highlighter disregard this possibility |
| 2025-11-19 15:45:37 +0100 | trickard | (~trickard@cpe-62-98-47-163.wireline.com.au) (Ping timeout: 264 seconds) |
| 2025-11-19 15:45:25 +0100 | <chromoblob> | in normal usage, i don't |
| 2025-11-19 15:45:13 +0100 | trickard__ | (~trickard@cpe-62-98-47-163.wireline.com.au) |
| 2025-11-19 15:44:36 +0100 | <tomsmeding> | that's the big question here |
| 2025-11-19 15:44:16 +0100 | <tomsmeding> | chromoblob: why do you put spaces inside backticks |
| 2025-11-19 15:41:31 +0100 | spew | (~spew@user/spew) spew |
| 2025-11-19 15:39:50 +0100 | spew | (~spew@user/spew) (Ping timeout: 256 seconds) |
| 2025-11-19 15:39:40 +0100 | pr1sm | (~pr1sm@24.91.163.31) (Ping timeout: 264 seconds) |
| 2025-11-19 15:38:02 +0100 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) (Remote host closed the connection) |
| 2025-11-19 15:35:51 +0100 | weary-traveler | (~user@user/user363627) (Remote host closed the connection) |
| 2025-11-19 15:29:54 +0100 | <merijn> | It breaks on parameter substitutions, window functions, all kinds of other tiny things |
| 2025-11-19 15:29:35 +0100 | <merijn> | Everyone implements syntax highlighting for SELECT, create table, etc. but as soon as you do anything serious they're all like "lol, didn't implement that" |
| 2025-11-19 15:29:03 +0100 | <merijn> | I started a new project using SQLite, I didn't like the neovim syntax highlighting of SQL (it's a terrible "every dialect half-assed together" tree-sitter parser) breaking on every query, got side-tracked into yak-shaving by writing my own SQLite parser since no one made one for me |
| 2025-11-19 15:18:59 +0100 | <[exa]> | merijn: why'd you do a sqlite one |
| 2025-11-19 15:14:53 +0100 | pr1sm | (~pr1sm@24.91.163.31) |
| 2025-11-19 15:14:12 +0100 | spew | (~spew@user/spew) spew |
| 2025-11-19 15:06:47 +0100 | <merijn> | Maybe if I'm ever done writing my SQLite tree-sitter parser I will just write a Haskell parser from scratch |
| 2025-11-19 15:06:19 +0100 | <merijn> | It's like they looked at the tree-sitter documentation of keeping parse trees simple and small and being like...naah, fuck that |
| 2025-11-19 15:05:33 +0100 | <[exa]> | it's like if flex&yacc never happened |
| 2025-11-19 15:04:35 +0100 | <merijn> | [exa]: It's a nightmare |
| 2025-11-19 15:03:41 +0100 | <[exa]> | my eyes |
| 2025-11-19 15:03:39 +0100 | <[exa]> | merijn: man, I opened that |
| 2025-11-19 14:56:00 +0100 | simplystuart | (~simplystu@c-75-75-152-164.hsd1.pa.comcast.net) |