Nice! And thanks. Xpeg looks pretty cool. I think I’m going to try it for my library Mozart - a somewhat new take on BPM. I want to create a very readable textual syntax for my current struct based syntax. It might take me a while.
The last time I did any serious parsing was using Bison and Flex. Since Flex took care of tokenization, you didn’t have to account for spaces in your parse rules. It seems like this is not the case for Xpeg, NimbleParsec, etc. Do I have that right?
