1. 13
  1. 3

    This is essentially a parser combinator library, right? I’m just wondering why they omitted the term.

    1. 3

      It might be because they use the result builder pattern/feature of Swift.

      1. 3

        Yeah. They’ve called their parser stuff parser combinators before. On their homepage there’s five videos called “Parser Combinators: Part N” and “Parser Combinators Recap: Part N” but I guess they wanted to highlight that it’s using result builders now.