1. 28 Nov, 2017 1 commit
  2. 28 Feb, 2017 1 commit
  3. 05 Dec, 2016 1 commit
  4. 24 Oct, 2016 1 commit
    • verwaest's avatar
      Simplify and fix the rewriter · caba112d
      verwaest authored
      Now we
      - always set .result to undefined before a visited loop and switch since we can't know whether they will set a value,
      - only visit finally if it can break/continue; and only store/restore .result in that case
      
      BUG=
      
      Review-Url: https://codereview.chromium.org/2427253003
      Cr-Commit-Position: refs/heads/master@{#40542}
      caba112d
  5. 08 Apr, 2016 1 commit
  6. 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
  7. 03 Feb, 2016 1 commit
  8. 08 Oct, 2015 1 commit