1. 16 Mar, 2015 1 commit
  2. 13 Mar, 2015 2 commits
  3. 12 Mar, 2015 1 commit
  4. 10 Mar, 2015 1 commit
  5. 09 Mar, 2015 1 commit
  6. 06 Mar, 2015 2 commits
  7. 04 Mar, 2015 1 commit
  8. 02 Mar, 2015 1 commit
  9. 27 Feb, 2015 1 commit
  10. 26 Feb, 2015 2 commits
  11. 19 Feb, 2015 2 commits
  12. 17 Feb, 2015 3 commits
  13. 16 Feb, 2015 2 commits
  14. 11 Feb, 2015 1 commit
  15. 10 Feb, 2015 1 commit
  16. 09 Feb, 2015 2 commits
  17. 05 Feb, 2015 2 commits
  18. 04 Feb, 2015 1 commit
  19. 03 Feb, 2015 3 commits
  20. 02 Feb, 2015 1 commit
  21. 30 Jan, 2015 3 commits
  22. 29 Jan, 2015 1 commit
    • aperez's avatar
      Do not create unresolved variables when parsing arrow functions lazily · 91b87e7a
      aperez authored
      Arrow function parameter lists are parsed as expressions. When an identifier
      is found a VariableProxy is created and added to the list of unresolved
      variables for the scope. When parsing a function lazily, the scope has been
      already resolved, so with this patch only the VariableProxy is created,
      without adding it as an unresolved variable in the scope.
      
      BUG=v8:3501
      LOG=Y
      
      Review URL: https://codereview.chromium.org/880253004
      
      Cr-Commit-Position: refs/heads/master@{#26328}
      91b87e7a
  23. 28 Jan, 2015 1 commit
  24. 27 Jan, 2015 2 commits
  25. 26 Jan, 2015 2 commits