Skip to content

Decide on a parser #2

@wolfv

Description

@wolfv

When I forked deno_task_shell I tried to use a different parser, because I felt it might be easier to parse with a two-step approach (first tokenize, then parse).
I do not know much about parsers though.

deno_task_shell currently uses monch which is similar to nom but only for strings. It also lacks a few functions but they can usually easily be added (we could also fork monch here.

I also investigated chumsky: https://docs.rs/chumsky/latest/chumsky/ which looks like a cool parser project. Didn't really get anything to work with it, yet.

However, monch and the current parser could work and we might not need anything else! So maybe we should continue trying to extend it first.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions