1. 08 Apr, 2016 1 commit
  2. 22 Mar, 2016 1 commit
    • adamk's avatar
      Remove support for legacy const, part 1 · ed18aa65
      adamk authored
      Now that ES2015 const has shipped, in Chrome 49, legacy const declarations
      are no more. This lets us remove a bunch of code from many parts of the
      codebase.
      
      In this patch, I remove parser support for generating legacy const variables
      from const declarations. This also removes the special "illegal declaration"
      bit from Scope, which has ripples into all compiler backends.
      
      Also gone are any tests which relied on legacy const declarations.
      
      Note that we do still generate a Variable in mode CONST_LEGACY in one case:
      function name bindings in sloppy mode. The likely fix there is to add a new
      Variable::Kind for this case and handle it appropriately for stores in each
      backend, but I leave that for a later patch to make this one completely
      subtractive.
      
      Review URL: https://codereview.chromium.org/1819123002
      
      Cr-Commit-Position: refs/heads/master@{#35002}
      ed18aa65
  3. 05 Aug, 2015 1 commit
  4. 25 Jul, 2015 1 commit
    • littledan's avatar
      Split off a separate --harmony_sloppy_let flag · 2d2b72f6
      littledan authored
      --harmony_sloppy includes behavior to turn on sloppy mode lexical
      bindings. Before this patch, it also included a way to parse let
      which is likely web-incompatible (let is disallowed as an
      identifier). This patch splits off the let parsing from the more
      general block scoping code, so that block scoping can be developed
      independently.
      
      R=adamk
      LOG=N
      BUG=v8:3305
      
      Review URL: https://codereview.chromium.org/1255013002
      
      Cr-Commit-Position: refs/heads/master@{#29855}
      2d2b72f6
  5. 08 Jul, 2015 1 commit
  6. 13 Mar, 2015 1 commit
  7. 05 Mar, 2015 1 commit
  8. 03 Mar, 2015 1 commit
  9. 26 Nov, 2014 1 commit
    • dslomov's avatar
      harmony-scoping: make assignment to 'const' a late error. · 6ac4de87
      dslomov authored
      Per TC39 Nov 2014 decision.
      
      This patch also changes behavior for "legacy const": assignments to sloppy const in strict mode is now also a type error. This fixes v8:2243 and also brings us in compliance with other engines re assignment to function names (see updated webkit test), but might have bigger implications.
      That change can easily be reverted by changing Variable::IsSignallingAssignmentToConst.
      
      BUG=v8:3713,v8:2243
      LOG=N
      
      Review URL: https://codereview.chromium.org/749633002
      
      Cr-Commit-Position: refs/heads/master@{#25516}
      6ac4de87
  10. 17 Jun, 2014 1 commit
  11. 05 Dec, 2011 1 commit