4 Commits

Author	SHA1	Message	Date
Mike Pennisi	81d00def42	Force "early error" tests to fail if evaluated ... This pattern makes expectations more explicit by making test files more literal.	2017-06-28 11:24:36 -04:00
Leo Balter	6030e4ed71	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 11:34:59 -04:00
Mike Pennisi	7d4b1d28ae	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-10-19 15:24:21 -04:00
Brian Terlson	dbf251586e	Add tests for async functions ... Closes #479	2016-07-28 15:11:28 -07:00