swift-parsing VS Swift-ParserKit

No idea about parsing and evaluating in the same library, but there’s an excellent parser library from PointFree.

Sorry about that, broken links have been fixed in the episode and here's a link to the library: https://github.com/pointfreeco/swift-parsing.

If you want to do parsing, I strongly recommend Point-Free's Parsing library!

Honestly I still have a difficult time understanding Regex’s, and maintaining them can be hard since once small change can completely change how the Regex works. I would instead opt for a real parsing library, like for instance PointFree’s swift-parsing, who’s clear and idiomatic API makes it easy to understand what’s really going on. It’s also very, very performant - almost as performant as making a custom hand-rolled parser.

Personally, I would pull out my parser library and use that (the documentation is lacking, so if you're just starting out it can be hard to figure out what's going on, but you could use Point Free's parser library to do it like so:

I’m currently using the composable architecture. TCA is the result of video series by Point Free that discusses what Apple provides with SwiftUI, in detail, and iterates though the of the evolution of the architecture, to fill in the gaps. Most of the content is available by subscription, but there is free content as well, which includes a four part overview on the architecture itself. I highly recommend subscribing as the detailed walkthrough of building the architecture is extremely useful and helps clarify some of the more complicated aspects of its use.

I have a small but well-documented parser-combinator library, and one of the examples is a simple PEMDAS parser, which I'm sure you could extend to include func(arg) -style named function calls.

I've been working on a library for parser-combinators!

You can check out the quickstart which will give you an idea of what it's like to actually use parser combinators.

You can find it here, don't forget to build the documentation (Product > Build Documentation or Ctrl-Shift-Cmd-D)!