-
Toon Verwaest authored
The embedder should ultimately be responsible for handling this since they anyway give us a copy of the data. They can easily make sure that the chunks we get do not have lonely bytes. Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng Change-Id: Ie862107bbbdd00c4d904fbb457a206c2fd52e5d0 Reviewed-on: https://chromium-review.googlesource.com/1127044Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Marja Hölttä <marja@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#54262}
c7ad1ddd
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
libplatform | Loading commit data... | |
APIDesign.md | ||
DEPS | ||
OWNERS | ||
PRESUBMIT.py | ||
v8-inspector-protocol.h | ||
v8-inspector.h | ||
v8-platform.h | ||
v8-profiler.h | ||
v8-testing.h | ||
v8-util.h | ||
v8-value-serializer-version.h | ||
v8-version-string.h | ||
v8-version.h | ||
v8.h | ||
v8config.h |