• Patrick Thier's avatar
    Improve error messages for property access on null/undefined · 24c626c1
    Patrick Thier authored
    Only print the property name when accessing null/undefined if we can
    convert it to a string without causing side effects.
    If we can't, omit the property name in the error message.
    This should avoid confusion when the key is an object with toString().
    E.g. undefined[{toString:()=>'a'}] doesn't print 'read property [object
    Object]' anymore, which was misleading since the property accessed would
    be 'a', but we can't evaluate the key without side effects.
    
    Bug: v8:11365
    Change-Id: If82d1adb42561d4851e2bd2ca297a1c71738aee8
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2960211Reviewed-by: 's avatarToon Verwaest <verwaest@chromium.org>
    Commit-Queue: Patrick Thier <pthier@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#75250}
    24c626c1
Name
Last commit
Last update
..
bytecode_expectations Loading commit data...
bytecode-expectations-printer.cc Loading commit data...
bytecode-expectations-printer.h Loading commit data...
generate-bytecode-expectations.cc Loading commit data...
interpreter-tester.cc Loading commit data...
interpreter-tester.h Loading commit data...
source-position-matcher.cc Loading commit data...
source-position-matcher.h Loading commit data...
test-bytecode-generator.cc Loading commit data...
test-interpreter-intrinsics.cc Loading commit data...
test-interpreter.cc Loading commit data...
test-source-positions.cc Loading commit data...