-
Stefano Sanfilippo authored
In the current state, when unconditional compilation is on, strings are evaluated and other objects are passed through unchanged. After this, non-strings are passed to the modifying callback which could unwrap and eval them. eval(string) is not affected. If a non-modifying callback is set, it still takes the precedence, and the non-string object is returned as it would be currently (line 1933). Change-Id: I835b976b3420635baba245c08f8563a9e5b3b246 Bug: chromium:1024786 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1917147 Commit-Queue: Stefano Sanfilippo <ssanfilippo@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Michael Stanton <mvstanton@chromium.org> Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org> Cr-Commit-Position: refs/heads/master@{#67570}
0c9a0072
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
benchmarks | ||
cctest | ||
common | ||
debugger | ||
debugging | ||
fuzzer | ||
inspector | ||
intl | ||
js-perf-test | ||
memory | ||
message | ||
mjsunit | ||
mkgrokdump | ||
mozilla | ||
test262 | ||
torque | ||
unittests | ||
wasm-api-tests | ||
wasm-js | ||
wasm-spec-tests | ||
webkit | ||
BUILD.gn | ||
OWNERS |