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.

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

Use with verbose-errors feature #17

Closed
AljoschaMeyer opened this issue Jun 21, 2018 · 5 comments
Closed

Use with verbose-errors feature #17

AljoschaMeyer opened this issue Jun 21, 2018 · 5 comments
Assignees
Labels

Comments

@AljoschaMeyer
Copy link

Hey,

is it possible to use this crate with nom's verbose-errors feature? Enabling the verbose-errors feature for nom_locate does not help, compilation still fails here.

    |
279 |                 match e {
    |                       ^ pattern `Error(List(_))` not covered

nom version 4.0.0, nom_locate version 0.3.0

@progval progval self-assigned this Jun 21, 2018
@progval progval added the bug label Jun 21, 2018
progval added a commit to progval/nom_locate that referenced this issue Jun 21, 2018
@progval
Copy link
Collaborator

progval commented Jun 21, 2018

Thanks for the report, this should be fixed by commit c97835d.

@progval progval closed this as completed Jun 21, 2018
@AljoschaMeyer
Copy link
Author

Yay, thank you for the quick fix.

@tstack
Copy link

tstack commented Jan 3, 2019

Looks like this is broken again:

error[E0004]: non-exhaustive patterns: `Error(List(_))` not covered
   --> /Users/stack/.cargo/registry/src/github.com-1ecc6299db9ec823/nom_locate-0.3.1/src/lib.rs:299:23
    |
299 |                 match e {
    |                       ^ pattern `Error(List(_))` not covered

error[E0004]: non-exhaustive patterns: `Error(List(_))` not covered
   --> /Users/stack/.cargo/registry/src/github.com-1ecc6299db9ec823/nom_locate-0.3.1/src/lib.rs:324:23
    |
324 |                 match e {
    |                       ^ pattern `Error(List(_))` not covered

@progval
Copy link
Collaborator

progval commented Jan 3, 2019

@tstack You need to enable the verbose-errors feature of nom_locate (in addition to nom itself).

@tstack
Copy link

tstack commented Jan 3, 2019

Sorry, didn't realize, my bad.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants