| 10 Dec 2025 |
 kloenk | also do quite a bit of parser dev currently for a project :)
decided against chumsky as I also wanted to have the possibility to add a lsp and formatter later. Currently using ariadne as well for error reporting. did consider looking at miette (miette has a magic flag to create screen reader friendly output) | 15:32:11 |
 piegames | Yeah I've heard that of miette, which is really nice | 15:32:43 |
| piegames | Though on a first glance the ariadne API seems a lot simpler | 15:32:55 |
 Charles | hmm what about chumsky precludes its use for LSPs and formatters? | 15:34:30 |
| kloenk | my want for a lossless syntax tree. Chumsky apparently can somehow integrate into rowan, but found it so painful that I decided to use logos and do it with only logos | 15:35:09 |
| Charles | oh right yeah i forgot to mention rowan exists | 15:35:29 |
| kloenk | yeah that is true. and apparently they have a todo for screen reader output so maybe at some point | 15:35:52 |
| piegames | For lix performance will be key and everything else will require a secondary parser. Maybe even error handling will get a secondary parser | 15:35:59 |
| piegames | In reply to @kloenk:kloenk.eu
my want for a lossless syntax tree. Chumsky apparently can somehow integrate into rowan, but found it so painful that I decided to use logos and do it with only logos With lossless syntax tree you mean CST? | 15:36:19 |
| kloenk | then cumsky could be interesting. but apparently it's a pain with the type signatures. My (kconfig) project sadly is single threaded either way as the language is shit | 15:36:46 |
| kloenk | yeah I think that's the same. never exatly sure what is what | 15:37:00 |
