Skip to content
Snippets Groups Projects
  1. Mar 10, 2015
  2. Mar 07, 2015
  3. Mar 06, 2015
  4. Mar 05, 2015
  5. Mar 04, 2015
  6. Mar 03, 2015
  7. Feb 27, 2015
  8. Feb 25, 2015
  9. Feb 24, 2015
  10. Feb 19, 2015
  11. Feb 16, 2015
  12. Feb 12, 2015
  13. Feb 11, 2015
  14. Feb 09, 2015
  15. Feb 06, 2015
    • Steffen Müthing's avatar
      [Utility] Add infrastructure to handle operator->() for both lvalues and proxies · 7623a530
      Steffen Müthing authored
      If an iterator facade (like entity iterators) wants to allow the
      embedded implementation to return either an (internally stored)
      reference or a temporary object and expose these two behaviors to enable
      performance optimizations, operator->() needs special handling: If the
      implementation returns a reference, operator->() in the facade can
      simply return the address of the referenced object, but if the returned
      object is a temporary, we need to capture and store it in a helper
      object to make sure it outlives the member access.
      
      This patch adds a little helper function that tansparently handles both
      cases.
      7623a530
    • Dominic Kempf's avatar
    • Steffen Müthing's avatar
      [ForLoop] Port ForLoop TMP to C++11 · 732ca75c
      Steffen Müthing authored
      The ForLoop TMP used to put a number of restrictions on the arguments to
      apply(), mainly due to the limited capabilities of C++01 wrt. to
      argument forwarding.
      
      But now we have C++11, so we can throw away all that awkward code and
      replace it with a single forwarding function that supports arbitrary
      numbers of arbitrary combinations of lvalues and rvalues - all hail
      variadic templates and perfect forwarding!
      732ca75c
Loading