Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Should we move the parser engine to a separate crate? #20

Open
zrzka opened this issue Nov 29, 2019 · 0 comments
Open

Should we move the parser engine to a separate crate? #20

zrzka opened this issue Nov 29, 2019 · 0 comments
Labels
question Further information is requested

Comments

@zrzka
Copy link
Collaborator

zrzka commented Nov 29, 2019

Version 0.1.6 hides the State, Engine & Provide types. Basically the whole src/parser/engine.rs content.

  • Should we move it into separate anes-parser crate for example?
  • Like provide a crate with the parser only (no meaning, just input -> valid generic esc/csi sequence)?
@zrzka zrzka added the question Further information is requested label Nov 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zrzka