1. 27 Apr, 2016 3 commits
  2. 26 Apr, 2016 1 commit
  3. 25 Apr, 2016 1 commit
  4. 22 Apr, 2016 3 commits
  5. 21 Apr, 2016 1 commit
  6. 08 Apr, 2016 1 commit
  7. 07 Apr, 2016 1 commit
    • mike's avatar
      [es6] Fix bug in pattern re-writing · 9acbca18
      mike authored
      As originally implemented, a SingleNameBinding within a BindingPattern
      was incorrectly interpreted as an assignment if an initializer was
      present and that initializer was itself an AssignmentExpresion.
      For example:
      
          let x;
          { let [x = y = 1] = []; }
          print(x); // expected: undefined, actual: 1
      
      Extend the heuristic that detects the "context" of a destructuring
      pattern to account for AssignmentExpressions within SingleNameBindings.
      
      BUG=v8:4891
      LOG=N
      R=adamk@chromium.org
      
      Review URL: https://codereview.chromium.org/1859423002
      
      Cr-Commit-Position: refs/heads/master@{#35334}
      9acbca18
  8. 05 Apr, 2016 5 commits
  9. 04 Apr, 2016 1 commit
  10. 01 Apr, 2016 4 commits
  11. 31 Mar, 2016 1 commit
  12. 30 Mar, 2016 2 commits
  13. 28 Mar, 2016 2 commits
    • littledan's avatar
      Remove RegExp.prototype.source getter compat workaround · 80803aa8
      littledan authored
      The getter RegExp.prototype.source is specified in ES2015 to throw when
      called on a non-RegExp instance, such as RegExp.prototype. We had previously
      put in a compatibility workaround for all RegExp getters to make them
      throw on access specifically with RegExp.prototype as the receiver; however,
      we only have evidence that this is needed for properties other than source.
      This patch removes the compatibility workaround for get RegExp.prototype.source
      and gives it semantics precisely as per the ES2015 specification.
      
      R=adamk
      BUG=chromium:581577,v8:4827
      LOG=Y
      
      Review URL: https://codereview.chromium.org/1837843002
      
      Cr-Commit-Position: refs/heads/master@{#35086}
      80803aa8
    • adamk's avatar
      String.prototype.{match,search} should do only one RegExp brand check · 0fdf3255
      adamk authored
      Previously, they would check for Symbol.match/Symbol.search, and then
      do another check for Symbol.match in the RegExp constructor. This patch
      avoids the second one by skipping the RegExp constructor, as the spec does.
      
      Review URL: https://codereview.chromium.org/1840723002
      
      Cr-Commit-Position: refs/heads/master@{#35085}
      0fdf3255
  14. 25 Mar, 2016 1 commit
    • adamk's avatar
      Remove --harmony-regexps flag · 06403470
      adamk authored
      It's been on since M49. Also moved tests from harmony -> es6,
      one of which was merged with another test of the same name.
      
      While moving stuff over to regexp.js, I also noticed that there
      were unused calls to %FunctionSetName and %SetNativeFlag (those
      calls are already handled by InstallGetter()).
      
      Review URL: https://codereview.chromium.org/1838563003
      
      Cr-Commit-Position: refs/heads/master@{#35076}
      06403470
  15. 23 Mar, 2016 2 commits
  16. 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
  17. 21 Mar, 2016 2 commits
  18. 18 Mar, 2016 2 commits
  19. 16 Mar, 2016 2 commits
  20. 15 Mar, 2016 1 commit
  21. 11 Mar, 2016 2 commits
    • adamk's avatar
      Remove --harmony-tostring runtime flag · b16fc863
      adamk authored
      ES2015 Object.prototype.toString semantics were enabled in version 4.9,
      which has been in stable Chrome for nearly two weeks at this point.
      
      R=littledan@chromium.org
      
      Review URL: https://codereview.chromium.org/1784033002
      
      Cr-Commit-Position: refs/heads/master@{#34732}
      b16fc863
    • vogelheim's avatar
      Fix expression positions for for-loops. · de4f3d3e
      vogelheim authored
      FullCodegen generates 2 statement positions for the loop init block, like so:
      
        for(var i = 0; i....
            ^   ^
      
      This change removes the first of those, updates unit tests,
      and removes text expectations for Ignition.
      
      ---
      An alternative would be to emulate the existing behaviour in Ignition, but:
      - The new behaviour seems more logical,
      - Ignition generates no bytecodes for the 'var', meaning there is no code position to attach the break position to.
      
      BUG=v8:4690
      LOG=Y
      
      Review URL: https://codereview.chromium.org/1784883002
      
      Cr-Commit-Position: refs/heads/master@{#34717}
      de4f3d3e
  22. 10 Mar, 2016 1 commit