summaryrefslogtreecommitdiffstats
path: root/js/src/frontend/Parser.cpp
Commit message (Collapse)AuthorAgeLines
* 1317375 - Implement "Template Literals Revision / Lifting Template Literal ↵Gaming4JC2019-07-18-5/+20
| | | | Restriction" ECMAScript proposal
* 1317374 - Don't do Annex B lexical function behavior when redeclaring a ↵Gaming4JC2019-07-18-0/+6
| | | | parameter name.
* 1325157 - Implement a ParserBase class that holds functionality that's ↵Gaming4JC2019-07-18-50/+50
| | | | identical between syntax parsing and full parsing.
* 1320403 - Move JSFunction::EXPR_BODY to JSScript, LazyScript, and FunctionBox.Gaming4JC2019-07-18-5/+13
|
* 636635 - Do not create named lambda binding for a function created by ↵Gaming4JC2019-07-18-10/+11
| | | | Function constructor.
* 1317379 - Disallow generator functions and async functions as direct ↵Gaming4JC2019-07-18-21/+62
| | | | children of if/else.
* 1296814 - Move FunctionDeclaration-as-consequent/alternative handling out of ↵Gaming4JC2019-07-18-32/+24
| | | | Parser::functionStmt into Parser::consequentOrAlternative.
* 1317153 - Provide better error message when errornous syntax possibly match ↵Gaming4JC2019-07-18-33/+56
| | | | "await SOMETHING" outside async function.
* 1315815 - Don't treat async or await as a keyword when they contain escapes.Gaming4JC2019-07-18-39/+56
|
* Remove useless assert.wolfbeast2019-04-25-1/+0
| | | | Resolves #1055.
* Rename TokenStream::reportStrictWarningErrorNumberVA towolfbeast2019-04-06-2/+2
| | | | | | | TokenStream::reportExtraWarningErrorNumberVA for clarity. Emit Extra Warnings instead of Strict Warnings from the BCE where it makes sense.
* Remove Parser::reportHelper since it's no longer used.wolfbeast2019-04-06-24/+0
|
* Inline Parser::reportHelper into its callers.wolfbeast2019-04-06-8/+29
|
* Remove Parser::reportWithNode and its remaining callers.wolfbeast2019-04-06-23/+7
| | | | | All of the callsites have a full ParseNode* at hand, of which the offset can be directly accessed.
* Report errors for bad increment/decrement operands usingwolfbeast2019-04-06-29/+26
| | | | explicitly-specified offsets.
* Simplify checking of targets within destructuring patterns.wolfbeast2019-04-06-72/+14
|
* Simplify increment/decrement operand checking.wolfbeast2019-04-06-16/+18
|
* Inline Parser::checkAssignmentToCall into its sole caller.wolfbeast2019-04-06-14/+5
|
* Specify an explicit offset when reporting an error for a for-of loopwolfbeast2019-04-06-1/+1
| | | | whose target is an expression that begins with 'let'.
* Simplify checking of the left-hand side of assignment and compoundwolfbeast2019-04-06-46/+28
| | | | assignment expressions.
* Remove for-in/of loop parsing code that redundantly marks the loopwolfbeast2019-04-06-6/+0
| | | | target as assigned -- Parser::forHeadStart already does this.
* Report some errors about invalid left-hand-sides in for-in/of loop headswolfbeast2019-04-06-36/+26
| | | | using code with an explicitly computed offset.
* Report the error for uninitialized const-declaration in for(;;) loopwolfbeast2019-04-06-1/+1
| | | | head using an explicit offset.
* Remove Parser::reportWithOffset since it's no longer used.wolfbeast2019-04-06-12/+0
|
* Introduce Parser::warningAtwolfbeast2019-04-06-10/+16
| | | | | This reduces reporting an warning at a particular offset to its bare essentials, simplifying calls.
* Report for-loop-decl-with-initializer errors using a specified offsetwolfbeast2019-04-06-2/+2
| | | | instead of a node's offset.
* Report bad-class-member errors using a specified offset instead of a node's ↵wolfbeast2019-04-06-4/+4
| | | | offset.
* Remove Parser::reportBadReturnwolfbeast2019-04-06-20/+3
| | | | Report simpler errors that don't use the offset of a node as location.
* Introduce Parser::errorAtwolfbeast2019-04-06-32/+39
| | | | | This reduces reporting an error at a particular offset to its bare essentials, simplifying calls.
* Inline Parser::checkFunctionDefinition into its sole caller.wolfbeast2019-04-06-63/+49
|
* Inline GeneratorKindFromPropertyType and AsyncKindFromPropertyType.wolfbeast2019-04-06-20/+9
| | | | Trivially inlines these into their sole caller.
* Move the Parser::checkFunctionDefinition call into its callers.wolfbeast2019-04-06-86/+90
|
* Move part of Parser::functionDefinition into callers.wolfbeast2019-04-06-17/+29
|
* Track strict mode errors in for...in and for...of correctly whenwolfbeast2019-04-05-4/+5
| | | | syntax-parsing.
* Track strict mode errors in unary deletions correctly whenwolfbeast2019-04-05-2/+17
| | | | syntax-parsing.
* Specify an explicit offset when warning about "use asm" found in thewolfbeast2019-04-05-4/+5
| | | | directive prologue of a script (rather than a function body).
* Change report at current offset to warning(), extraWarning() and error()wolfbeast2019-04-05-121/+140
|
* Remove the |bool strict| argument from the report-at-current-offsetwolfbeast2019-04-05-124/+132
| | | | | Parser function (zeport). zeport => qeport
* Split Parser::report into Parser::zeport (a temporary name) that useswolfbeast2019-04-05-201/+186
| | | | | the current offset, and Parser::reportWithNode that derives it from a Node.
* Stage 1-1: Implement Function.prototype.toString revision proposal.wolfbeast2019-02-02-57/+110
| | | | Tag #960
* Remove telemetry leftovers from JS engine.adeshkp2019-01-30-13/+0
|
* Call the relevant scope-data constructor when allocating it, and poison/mark ↵trav902018-09-02-5/+3
| | | | as undefined the memory for the trailing array of BindingNames, ratther than impermissibly PodZero-ing non-trivial classes.
* Convert the trailing array of BindingNames at the end of the various kinds ↵trav902018-09-02-33/+43
| | | | of scope data into raw unsigned chars into which those BindingNames are placement-new'd, rather than memcpy-ing non-trivial classes around and failing to comply with the C++ object model
* Silence for-each-in warningswolfbeast2018-04-05-2/+3
|
* Follow up: A opening bracket { was added; Added "function()->explicitName()" ↵janekptacijarabaci2018-03-19-1/+1
| | | | | | instead of "function()->name()" Issue #78
* Part 1: Implement ES6 function name property semanticsjanekptacijarabaci2018-03-19-10/+25
| | | | Issue #78
* Bug 1320388: Move JSFunction::HAS_REST to JSScript and LazyScriptjanekptacijarabaci2018-03-19-4/+4
| | | | | | Issue #78 [Depends on] Bug 883377: Implement ES6 function "name" property semantics
* Bug 755821: Function() should use the parser's argument parsing codejanekptacijarabaci2018-03-16-33/+22
|
* Add m-esr52 at 52.6.0Matt A. Tobin2018-02-02-0/+9627
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-23 18:02:00 +0000