1. 27 Feb, 2017 1 commit
  2. 04 Nov, 2016 1 commit
  3. 28 Sep, 2016 1 commit
  4. 06 May, 2016 1 commit
    • ulan's avatar
      [API] Remove deprecated WeakCallbackData and related functions. · 82dcb2be
      ulan authored
      This removes:
      - PersistentBase::SetWeak that takes WeakCallbackData.
        The embedders should use the version that takes WeakCallbackInfo.
      - PersistentBase::SetPhantom.
        The embedders should SetWeak that takes WeakCallbackInfo.
      
      Functions in DefaultPersistentValueMapTraits are changed to accept
      WeakCallbackInfo instead of WeakCallbackData.
      
      BUG=chromium:609808
      LOG=NO
      
      Review-Url: https://codereview.chromium.org/1953263002
      Cr-Commit-Position: refs/heads/master@{#36079}
      82dcb2be
  5. 15 Apr, 2016 1 commit
  6. 03 Sep, 2015 1 commit
  7. 15 Jul, 2015 1 commit
  8. 22 Apr, 2015 1 commit
  9. 10 Apr, 2015 1 commit
  10. 26 Mar, 2015 1 commit
  11. 24 Mar, 2015 1 commit
  12. 09 Mar, 2015 1 commit
    • dcarney's avatar
      remove phantom naming from the api · 60c1ad02
      dcarney authored
      since the old style weakness is slated for removal, we might as well reuse the name to limit confusion.  additionally I simplified the callback type to a enum to either get internal field values or not
      
      this should be a non-breaking change with the exception of PhantomPersistentValueMap, which is unused.
      
      R=jochen@chromium.org, erikcorry@chromium.org
      
      BUG=
      
      Review URL: https://codereview.chromium.org/989153003
      
      Cr-Commit-Position: refs/heads/master@{#27084}
      60c1ad02
  13. 23 Jan, 2015 1 commit
  14. 10 Jun, 2014 1 commit
  15. 27 May, 2014 1 commit
  16. 09 May, 2014 1 commit
  17. 29 Apr, 2014 1 commit
  18. 02 Apr, 2014 1 commit
  19. 01 Apr, 2014 1 commit
  20. 31 Mar, 2014 1 commit
  21. 28 Mar, 2014 1 commit
    • marja@chromium.org's avatar
      Amend PersistentValueMap: · 6730ec84
      marja@chromium.org authored
      - Use the surrounding map (instead of Traits::Impl) for weak callback.
      - Provide for a fast reference to a mapped value.
      - Restructure Traits to accomondate for the first point above.
      
      [Why?] As discussed, I proceeded to replace Impl with the map.
      The problem I encountered with that version is that now the
      Traits class depends on itself: The weak-related methods require the
      map type in their signature. But the map type includes the Traits class
      and hence the Traits class method signatures depend on the specific Traits class. That
      makes them practically un-derivable: While you can derive a Traits class
      from another one, since the compiler now expects methods with a different
      signature. To accommodate, I pulled the dispose traits into the weak traits
      class. I also removed the Impl*/MapType* parameter from the Dispose call,
      since no implementation seems to need it.
      
      R=dcarney@chromium.org
      BUG=
      
      Review URL: https://codereview.chromium.org/212893007
      
      Patch from Daniel Vogelheim <vogelheim@chromium.org>.
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@20326 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      6730ec84
  22. 19 Mar, 2014 1 commit
  23. 18 Mar, 2014 2 commits
  24. 14 Mar, 2014 1 commit