v8/test/mjsunit/regress/string-next-encoding.js
Sigurd Schneider 35bce874d4 [turbofan] Fix encoding issue in string iteration
This fixes %StringIteratorPrototype%.next to not mixup
UTF16 and UTF32, and consistently use UTF32 for now.

Bug: chromium:805855
Change-Id: If58e2fe0d9bebd894e12abf8af82881c74388294
Reviewed-on: https://chromium-review.googlesource.com/888741
Commit-Queue: Sigurd Schneider <sigurds@chromium.org>
Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#50886}
2018-01-26 11:12:08 +00:00

21 lines
526 B
JavaScript
Raw Blame History

// Copyright 2018 the V8 project authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.
// Flags: --opt --allow-natives-syntax
function f() {
var s = "äϠ<C3A4>𝌆";
var i = s[Symbol.iterator]();
assertEquals("ä", i.next().value);
assertEquals("Ϡ", i.next().value);
assertEquals("<22>", i.next().value);
assertEquals("𝌆", i.next().value);
assertSame(undefined, i.next().value);
}
f();
f();
%OptimizeFunctionOnNextCall(f);
f();