nanopass-framework-scheme VS flatparse

Well, this compiler framework in scheme might be worth looking.

Some serious level Conway's Law. I mean multipass isn't bad. It composes well, it minimizes coupling, etc etc. It doesn't necessarily have to hit disk, any store could be used. I myself like multipass taken to an extreme in nanopass, but at the same time, I absolutely adore the single pass nature of Wirthian languages.

I am trying to use the nanopass framework with guile. I do not get that far :D I can't seem to figure out how guile's %load-path works.

I'd say Rust is the absolute best (by a considerable margin) for a production-ready implementation. For a compiler's course it should be a fine choice, but I'd also look at OCaml+Menhir or Scheme+nanopass as alternatives.

Initially Happy/Alex was almost 5x slower than the fastest implementation. Using an explicit export list and generating the parser with the experimental --strict flag from happy brought it down to a manageable 3.2x slowdown. The fastest parser was surprisingly not my handwritten example, but the one written using the parser combinator library flatparse.

Flatparse has some microbenchmarks showing 60x speed difference compared to Parsec, and 10x-20x compared to Attoparsec or Megaparsec.