You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The recent breaking change described in #41100 changes UTF-8 encoding such that lone surrogates are encoded as replacement characters. However, this change did not extend to the print implementation in the VM, which contains its own UTF-8 encoder.
This causes the failures seen in https://dart-review.googlesource.com/c/sdk/+/149285 where a test outputs surrogates via print (which are encoded directly) and the Dart implementation running the test system is updated to treat encoded surrogates as invalid.
We should change the UTF-8 encoder used in print (when not overridden by the embedder) to match the behavior of our Dart UTF-8 encoder.
The text was updated successfully, but these errors were encountered:
askeksa-google
added
the
area-vm
Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.
label
May 28, 2020
The recent breaking change described in #41100 changes UTF-8 encoding such that lone surrogates are encoded as replacement characters. However, this change did not extend to the
print
implementation in the VM, which contains its own UTF-8 encoder.This causes the failures seen in https://dart-review.googlesource.com/c/sdk/+/149285 where a test outputs surrogates via
print
(which are encoded directly) and the Dart implementation running the test system is updated to treat encoded surrogates as invalid.We should change the UTF-8 encoder used in
print
(when not overridden by the embedder) to match the behavior of our Dart UTF-8 encoder.The text was updated successfully, but these errors were encountered: