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

decode::Error::unexpected_field should take &[u8] #23

Open
thequux opened this issue Jul 18, 2019 · 0 comments
Open

decode::Error::unexpected_field should take &[u8] #23

thequux opened this issue Jul 18, 2019 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@thequux
Copy link
Contributor

thequux commented Jul 18, 2019 •
edited
Loading

The name of an unexpected field is generally available to client code as a &[u8]; it would be much more convenient to be able to report that directly than to have to convert it to a string (for example).

This would likely be a breaking change, thus necessitating a v0.3.0
@0ndorio 0ndorio added enhancement New feature or request good first issue Good for newcomers labels Jul 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@thequux @0ndorio