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/object/method-definition/early-errors-object-method-...

18 lines
380 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>
esid: pending
description: >
Early error rules for StrictFormalParameters are applied
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
---*/
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
Move `throw "…"` for negative parsing errors to a helper function Closes #1634.
2018-09-27 01:18:22 +02:00
failIfCodeGetsEvaluated();
Update object literal expressions for readability After @rwaldron's feedback: The purpose of the `!` operator is to evaluate an UnaryExpression, coerce the result to a boolean value and then return the negated value of that operation. But that's not what you're trying to do at all—you just want to evaluate the expression to the right of the operator, nothing more, nothing less. In this specific case, you don't even really care about the evaluation, the goal is write valid (or invalid, as the case may be) syntax that is will be parsed according to a specific grammar rule that requires some operator to signal that the thing is an expression and not a Block Statement.
2017-04-07 17:34:55 +02:00
({
Add tests for async functions Closes #479
2016-01-26 23:31:32 +01:00
async foo(a, a) { }
Update object literal expressions for readability After @rwaldron's feedback: The purpose of the `!` operator is to evaluate an UnaryExpression, coerce the result to a boolean value and then return the negated value of that operation. But that's not what you're trying to do at all—you just want to evaluate the expression to the right of the operator, nothing more, nothing less. In this specific case, you don't even really care about the evaluation, the goal is write valid (or invalid, as the case may be) syntax that is will be parsed according to a specific grammar rule that requires some operator to signal that the thing is an expression and not a Block Statement.
2017-04-07 17:34:55 +02:00
})