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

ParseMode #65

Open
alexkazik opened this issue Oct 17, 2017 · 1 comment
Open

ParseMode #65

alexkazik opened this issue Oct 17, 2017 · 1 comment

Comments

@alexkazik
Copy link

Since myDefaultParseMode should not be used it's probably better to crate new functions which replace parseExp and the others and take a ParseMode as an parameter.
@JonasDuregard JonasDuregard mentioned this issue Jun 20, 2018
Closed
@JonasDuregard
Copy link
Collaborator

How about a parseWithExts that takes a list of known extensions and enables them? (almost always the only part of the ParseMode anyone edits?)

Arguably, the default mode for parseExp and friends should enable all extensions that HSM is known to support properly (and none that it is known not to support).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JonasDuregard @alexkazik