Enforce unescape functions to operate over UTF-8 and fix serde bugs #421
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
They are always operate over UTF-8 input, but that was not reflected in types.
This PR also fixes a bug in the serde deserializer: the order of unescape and decode operations was swapped. Although we are still going to abandon decoding on demand, it is still need to mention this fix in the changelog.
Also, because of new encoding policy, deserializing of bytes content using serde now disallowed. This is anyway works incorrectly, because XML is not able to store binary data, they are always should be encoded in some way. Now this is enforced by deserializer and allows us to decode all input at once ans work with UTF-8 representation internally.