Sven Sauleau 5bdb13297f [wasm] merge js constants file in module-builder ... We noticed that almost every call site were loading both files, the split isn't necessary anymore. In some message tests, removed the absolute line number to allow future changes. Bug: v8:8726 Change-Id: I8527f0a1ecfa685aa01a5e2f5f47ddf1cb13a545 Reviewed-on: https://chromium-review.googlesource.com/c/1446452 Commit-Queue: Sven Sauleau <ssauleau@igalia.com> Reviewed-by: Ben Titzer <titzer@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#59220}		2019-01-30 22:10:34 +00:00
..
assert_true.js
assert_true.out
assert-promise-result-rejects-empty.js
assert-promise-result-rejects-empty.out
assert-promise-result-rejects-with-throw-empty.js
assert-promise-result-rejects-with-throw-empty.out	WIP: [parser] Fix arrow function name inferring	2019-01-08 08:10:03 +00:00
assert-promise-result-rejects.js
assert-promise-result-rejects.out	WIP: [parser] Fix arrow function name inferring	2019-01-08 08:10:03 +00:00
assert-promise-result-resolves.js
assert-promise-result-resolves.out	WIP: [parser] Fix arrow function name inferring	2019-01-08 08:10:03 +00:00
assert-promise-result-wasm-compile-fail.js	[wasm] merge js constants file in module-builder	2019-01-30 22:10:34 +00:00
assert-promise-result-wasm-compile-fail.out	[wasm] merge js constants file in module-builder	2019-01-30 22:10:34 +00:00