`decode::Error::unexpected_field` should take `&[u8]`
thequux opened this issue · 0 comments
thequux commented
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