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/expressions/async-arrow-function/early-errors-arrow-duplicat...

35 lines
918 B
JavaScript
Raw Normal View History

Add tests for async functions Closes #479
2016-01-26 23:31:32 +01:00
// Copyright 2016 Microsoft, Inc. All rights reserved.
// This code is governed by the BSD license found in the LICENSE file.
/*---
author: Brian Terlson <brian.terlson@microsoft.com>
Improve coverage for UniqueFormalParameters (#2043) Previously, the early error prohibiting duplicate entries in UniqueFormalParameters was only tested in terms of async functions. In one case, this was misattributed to UniqeFormalParameters and only enforced for strict mode code. Extend coverage to the other function-creating productions which include UniqueFormalParameters (i.e. method definitions and non-async arrow functions), and update the existing tests to more accurately describe the source of the error.
2019-01-23 17:07:19 +01:00
esid: sec-async-arrow-function-definitions
description: Formal parameters may not contain duplicates
info: |
# 14.2 Arrow Function Definitions
When the production
ArrowParameters:CoverParenthesizedExpressionAndArrowParameterList
is recognized the following grammar is used to refine the interpretation
of CoverParenthesizedExpressionAndArrowParameterList:
ArrowFormalParameters[Yield, Await]:
(UniqueFormalParameters[?Yield, ?Await])
# 14.1.2 Static Semantics: Early Errors
UniqueFormalParameters:FormalParameters
- It is a Syntax Error if BoundNames of FormalParameters contains any
duplicate elements.
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 async functions Closes #479
2016-01-26 23:31:32 +01:00
---*/
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 async functions Closes #479
2016-01-26 23:31:32 +01:00
async(a, a) => { }