v8/test/message/fail/import-as-eval.out

*%(basename)s:5: SyntaxError: Unexpected eval or arguments in strict mode
import { foo as eval } from "mod";
                ^^^^
SyntaxError: Unexpected eval or arguments in strict mode
[test] Remove module pragma in favor of .mjs d8 treats files with the .mjs extension as modules instead of classic scripts. Thus, the `// MODULE` pragma and its corresponding logic in test runners can be removed in favor of explicitly adding the extension. Bug: v8:7950, v8:9395, v8:9406 Also-By: tmrts@chromium.org Change-Id: Ic74328dc5c5f176bb4bdf6d74bdd4d3966279ba5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1675958 Commit-Queue: Mathias Bynens <mathias@chromium.org> Reviewed-by: Tamer Tas <tmrts@chromium.org> Auto-Submit: Mathias Bynens <mathias@chromium.org> Cr-Commit-Position: refs/heads/master@{#62421} 2019-06-27 10:49:03 +00:00			`*%(basename)s:5: SyntaxError: Unexpected eval or arguments in strict mode`
Simplify error message logic in ParseImportNames The new logic ensures that the error messages are the same in the "import { <reserved word> }" and "import { foo as <reserved ord> }" cases. Also prepares ParseImportNames for returning both the import and local names to ParseImportClause. BUG=v8:1569 LOG=n Review URL: https://codereview.chromium.org/952863006 Cr-Commit-Position: refs/heads/master@{#26863} 2015-02-25 19:40:39 +00:00			`import { foo as eval } from "mod";`
			`^^^^`
			`SyntaxError: Unexpected eval or arguments in strict mode`