summaryrefslogtreecommitdiffstats
path: root/js/src/frontend
Commit message (Collapse)AuthorAgeLines
* 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-50/+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-38/+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-12/+19
| | | | | 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-22/+3
| | | | Report simpler errors that don't use the offset of a node as location.
* Introduce Parser::errorAtwolfbeast2019-04-06-32/+42
| | | | | 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-65/+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-94/+115
|
* Move part of Parser::functionDefinition into callers.wolfbeast2019-04-06-20/+31
|
* 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/+24
| | | | syntax-parsing.
* Specify an explicit offset when warning about "use asm" found in thewolfbeast2019-04-05-6/+7
| | | | directive prologue of a script (rather than a function body).
* Change report at current offset to warning(), extraWarning() and error()wolfbeast2019-04-05-122/+152
|
* Remove the |bool strict| argument from the report-at-current-offsetwolfbeast2019-04-05-125/+140
| | | | | Parser function (zeport). zeport => qeport
* Split Parser::report into Parser::zeport (a temporary name) that useswolfbeast2019-04-05-209/+198
| | | | | the current offset, and Parser::reportWithNode that derives it from a Node.
* Stage 1-1: Implement Function.prototype.toString revision proposal.wolfbeast2019-02-02-76/+154
| | | | Tag #960
* Remove telemetry leftovers from JS engine.adeshkp2019-01-30-15/+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-36/+47
| | | | 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
|
* Bug 1360839 - Call IteratorClose due to abrupt completion from yieldjanekptacijarabaci2018-03-25-9/+65
| | | | Issue #74
* Bug 1357075 - Pad a nop to unwind to the scope just before a destructuring ↵janekptacijarabaci2018-03-25-0/+8
| | | | | | iterator close trynote Issue #74
* Bug 1346862 - Fix IteratorClose due to non-local jumps being catchable by ↵janekptacijarabaci2018-03-25-15/+7
| | | | | | try statements inside for-of Issue #74
* Bug 1342553, Bug 1343072, Bug 1344753 (details in the description)janekptacijarabaci2018-03-25-148/+311
| | | | | | | | | | Bug 1342553 - Part 0.1: Use try-catch for IteratorClose in for-of Bug 1343072 - Update HasLiveStackValueAtDepth to follow the change in JSTRY_FOR_OF Bug 1344753 - Update for-of stack depth in ControlFlowGenerator::processWhileOrForInLoop Issue #74
* Bug 1338796 - Do not call iterator.return if iterator.throw is present in yield*janekptacijarabaci2018-03-25-125/+159
| | | | Issue #74
* Bug 1322069 - Add TryEmitterjanekptacijarabaci2018-03-25-169/+341
| | | | Issue #74
* Bug 1334799 - Handle stack value in correct order when leaving for-of loop ↵janekptacijarabaci2018-03-25-3/+3
| | | | | | from finally block Issue #74
* Bug 1332881 - Handle stack value in correct order when leaving loop and ↵janekptacijarabaci2018-03-25-0/+6
| | | | | | try-finally Issue #74
* Bug 1147371: Implement calling IteratorClose and "return" on iterators in yield*janekptacijarabaci2018-03-24-28/+52
| | | | Issue #74
* Bug 1147371: Implement IteratorClose for array destructuringjanekptacijarabaci2018-03-24-93/+128
| | | | Issue #74
* Bug 1147371: Rename allowContentSpread to allowContentIterjanekptacijarabaci2018-03-24-11/+21
| | | | Issue #74
* Bug 1147371: Implement IteratorClose for for-ofjanekptacijarabaci2018-03-24-164/+461
| | | | Issue #74
* Bug 1204028: Evaluate LHS reference before RHS in destructuringjanekptacijarabaci2018-03-20-93/+202
| | | | | Issue #73 [Depends on] Bug 1147371: Implement IteratorClose
* Bug 1322314 - Do not emit ParseNode twice in ↵janekptacijarabaci2018-03-20-139/+119
| | | | | | | BytecodeEmitter::emitDestructuringOpsArray Issue #73 [Depends on] Bug 1147371: Implement IteratorClose
* Bug 1322314 - Disallow emitting ParseNode twicejanekptacijarabaci2018-03-20-31/+6
| | | | | Issue #73 [Depends on] Bug 1147371: Implement IteratorClose
* Follow up: A opening bracket { was added; Added "function()->explicitName()" ↵janekptacijarabaci2018-03-19-2/+2
| | | | | | instead of "function()->name()" Issue #78
* Part 2: Call NameFunctions after emittingjanekptacijarabaci2018-03-19-14/+15
| | | | Issue #78
* Part 1: Implement ES6 function name property semanticsjanekptacijarabaci2018-03-19-24/+178
| | | | Issue #78
* Bug 1320042: Rename BytecodeEmitter::emitConditionallyExecuted{SOMETHING} to ↵janekptacijarabaci2018-03-19-19/+18
| | | | | | | | BytecodeEmitter::emit{SOMETHING}InBranch Issue #78 [Depends on] Bug 883377: Implement ES6 function "name" property semantics
* Bug 1320388: Move JSFunction::HAS_REST to JSScript and LazyScriptjanekptacijarabaci2018-03-19-8/+14
| | | | | | Issue #78 [Depends on] Bug 883377: Implement ES6 function "name" property semantics
* Correctly tokenize valid JS names when using code points outside of BMP range.wolfbeast2018-03-18-8/+142
|\ | | | | | | | | | | This resolves #72. Merged remote-tracking branch 'janek/js_variable_unicode_1'
| * Correctly tokenize valid JS names when using Unicode mathematical ↵janekptacijarabaci2018-03-18-8/+142
| | | | | | | | | | | | alphanumeric symbols as variable name Issue https://github.com/MoonchildProductions/Pale-Moon/issues/1647
* | Bug 755821: Function() should use the parser's argument parsing codejanekptacijarabaci2018-03-16-128/+111
|/
* Add m-esr52 at 52.6.0Matt A. Tobin2018-02-02-0/+34450
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-15 03:49:14 +0000