| 24 Jun 2025 |
 sielicki | I'm not super committed to finishing it, but I've been toying around lately with replacing the nix lexer and parser with https://lexy.foonathan.net/ lately | 22:21:47 |
| sielicki | * I'm not super committed to finishing it, but I've been toying around lately with replacing the nix lexer and parser with https://lexy.foonathan.net/ | 22:21:53 |
| sielicki | the value here is primarily in parsing speed (see lexy benchmarks: https://lexy.foonathan.net/benchmark_json/ ) but also that it would be simple to have a unified parser between nix and json | 22:23:30 |
| sielicki | * the value here is primarily in parsing speed (see lexy benchmarks: https://lexy.foonathan.net/benchmark_json/ ) but also that it would be simple to have a unified parser between nix and json, and any other parsing that you should want nix to be capable of understanding | 22:24:08 |
| sielicki | it's trivial to write allocator-aware lexy parsers and/or parsers which defer subexpression parsing. ie: imagine a parser which, in its first pass, scans exclusively for path references and import statements, and aggressively schedules that io work before coming back to parse everything else. | 22:30:39 |
| sielicki | en.cppreference.com/w/cpp/execution can also play a role there | 22:31:33 |
| 25 Jun 2025 |
 jade_ | we use a different parser of similar vibes in lix | 05:13:34 |
| sielicki | what's lix? | 05:13:55 |
| jade_ | uhh, the other major nix implementation, https://lix.systems | 05:14:07 |
| jade_ | ours is using the pegtl library | 05:15:01 |
| sielicki | oh very cool, yeah this looks awesome | 05:18:46 |
|  gkak.laₛ changed their display name from gkaklas to gkak.laₛ. | 17:50:38 |
| 26 Jun 2025 |
|  mdaniels5757 joined the room. | 01:29:04 |
