tyler.durden
/
test262
mirror of https://github.com/tc39/test262.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
test262/test/language/module-code/parse-err-decl-pos-import-f...

16 lines
384 B
JavaScript
Raw Normal View History

Add tests for position of module declarations Assert that ImportDeclaration and ExportDeclaration match only the ModuleItem symbol. According to the definition of HostResolveImportedModule, it is acceptable for an implementation to throw a SyntaxError in the event that a requested module can neither be found nor created: > If a Module Record corresponding to the pair referencingModule, > specifier does not exist or cannot be created, an exception must be > thrown. In order to reliably detect a SyntaxError in response to the correct interpretation of the grammar (and not a SyntaxError from an *incorrect* interpretation of the grammar followed by a failure to resolve the requested module), the ModuleSpecifier of ExportDeclarations should describe a valid resource.
2016-02-18 22:17:21 +01:00
// Copyright (C) 2016 the V8 project authors. All rights reserved.
// This code is governed by the BSD license found in the LICENSE file.
/*---
description: Statement cannot contain an `import` declaration
Update meta data: `id` to `esid` The project's expected frontmatter tag name changed while these files were under review.
2016-03-11 01:46:46 +01:00
esid: sec-modules
Re-format tests for SyntaxErrors Authored via the following command: $ find test -type f -print0 | \ xargs -0 sed \ -i 's/^\(\s*\)negative:\s*SyntaxError\s*$/\1negative:\n\1 phase: early\n\1 type: SyntaxError/g'
2016-01-31 00:57:28 +01:00
negative:
Rename negative test "phase" for parsing Early errors may result from parsing the source text of a test file, but they may also result from parsing some other source text as referenced through the ES2015 module syntax. The latter form of early error is not necessarily detectable by ECMAScript parsers, however. Because of this, the label "early" is not sufficiently precise for all Test262 consumers to correctly interpret all tests. Update the "phase" name of "early" to "parse" for all those negative tests that describe errors resulting from parsing of the file's source text directly. A forthcoming commit will update the remaining tests to use a "phase" name that is more specific to module resolution.
2017-12-03 06:06:42 +01:00
phase: parse
Re-format tests for SyntaxErrors Authored via the following command: $ find test -type f -print0 | \ xargs -0 sed \ -i 's/^\(\s*\)negative:\s*SyntaxError\s*$/\1negative:\n\1 phase: early\n\1 type: SyntaxError/g'
2016-01-31 00:57:28 +01:00
type: SyntaxError
Add tests for position of module declarations Assert that ImportDeclaration and ExportDeclaration match only the ModuleItem symbol. According to the definition of HostResolveImportedModule, it is acceptable for an implementation to throw a SyntaxError in the event that a requested module can neither be found nor created: > If a Module Record corresponding to the pair referencingModule, > specifier does not exist or cannot be created, an exception must be > thrown. In order to reliably detect a SyntaxError in response to the correct interpretation of the grammar (and not a SyntaxError from an *incorrect* interpretation of the grammar followed by a failure to resolve the requested module), the ModuleSpecifier of ExportDeclarations should describe a valid resource.
2016-02-18 22:17:21 +01:00
flags: [module]
---*/
Rename to $DONOTEVALUATE per @leobalter's suggestion
2018-10-11 16:59:24 +02:00
$DONOTEVALUATE();
Force "early error" tests to fail if evaluated This pattern makes expectations more explicit by making test files more literal.
2017-04-29 22:31:08 +02:00
Add tests for position of module declarations Assert that ImportDeclaration and ExportDeclaration match only the ModuleItem symbol. According to the definition of HostResolveImportedModule, it is acceptable for an implementation to throw a SyntaxError in the event that a requested module can neither be found nor created: > If a Module Record corresponding to the pair referencingModule, > specifier does not exist or cannot be created, an exception must be > thrown. In order to reliably detect a SyntaxError in response to the correct interpretation of the grammar (and not a SyntaxError from an *incorrect* interpretation of the grammar followed by a failure to resolve the requested module), the ModuleSpecifier of ExportDeclarations should describe a valid resource.
2016-02-18 22:17:21 +01:00
for (const y in [])
import v from './decl-pos-import-for-in-const.js';