Commit fc8cc090 authored by Toon Verwaest's avatar Toon Verwaest Committed by Commit Bot

[runtime] drop explicit thinstring unwrapping, it's done in InternalizeName

BUG=

Change-Id: Ic651f90b074bb712a0a03d4076a7d976bdc41138
Reviewed-on: https://chromium-review.googlesource.com/448538Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
Commit-Queue: Toon Verwaest <verwaest@chromium.org>
Cr-Commit-Position: refs/heads/master@{#43549}
parent ff8b1abb
......@@ -55,14 +55,7 @@ static MaybeHandle<Object> KeyedGetObjectProperty(Isolate* isolate,
!receiver_obj->IsAccessCheckNeeded() && key_obj->IsName()) {
Handle<JSObject> receiver = Handle<JSObject>::cast(receiver_obj);
Handle<Name> key = Handle<Name>::cast(key_obj);
// Get to a ThinString's referenced internalized string, but don't
// otherwise force internalization.
if (key->IsThinString()) {
key_obj = key =
handle(Handle<ThinString>::cast(key)->actual(), isolate);
} else {
key_obj = key = isolate->factory()->InternalizeName(key);
}
key_obj = key = isolate->factory()->InternalizeName(key);
DisallowHeapAllocation no_allocation;
if (receiver->IsJSGlobalObject()) {
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment