tree 4368d9a4dc7e4e8d4fec744ade1f0641b0c8ed0d
parent a57ef1254bc2c805099a6b926ccd2318a5df7878
author Daniel Salazar Villarreal <villarreald@google.com> 1594167987 +0000
committer CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> 1594167987 +0000

[feedback] Decode a std::string instead of a VMO

* Initially we had chosen a VMO to avoid copying data between std::string and std::vector depending on what an encoding algorithm might need. However encoding algorithms usually take a char array as input and std::string can provide this. Furthermore std::string can support any char value such as '\0'.

TESTED=`crasher` (report ID a488e5b4f920229a)

Bug: 51563

Change-Id: I06a2eff4b079807dfe20ddecdac7c49684a54be4
Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/404915
Commit-Queue: Daniel Salazar Villarreal <villarreald@google.com>
Reviewed-by: Francois Rousseau <frousseau@google.com>
Testability-Review: Francois Rousseau <frousseau@google.com>