1. 21 Mar, 2016 1 commit
  2. 04 Mar, 2016 3 commits
  3. 01 Feb, 2016 1 commit
  4. 26 Dec, 2015 1 commit
  5. 24 Dec, 2015 1 commit
  6. 16 Nov, 2015 1 commit
  7. 07 Nov, 2015 2 commits
  8. 30 Oct, 2015 1 commit
  9. 21 Oct, 2015 1 commit
  10. 29 Sep, 2015 1 commit
  11. 15 Sep, 2015 3 commits
  12. 06 Sep, 2015 1 commit
  13. 02 Aug, 2015 1 commit
  14. 31 Jul, 2015 2 commits
  15. 29 Jul, 2015 1 commit
  16. 03 Jul, 2015 1 commit
  17. 12 Jun, 2015 1 commit
  18. 09 Jun, 2015 1 commit
  19. 20 May, 2015 2 commits
  20. 16 May, 2015 1 commit
  21. 10 May, 2015 1 commit
  22. 09 May, 2015 2 commits
  23. 06 May, 2015 1 commit
  24. 05 May, 2015 2 commits
  25. 28 Apr, 2015 1 commit
  26. 26 Apr, 2015 1 commit
  27. 25 Apr, 2015 2 commits
  28. 21 Apr, 2015 1 commit
    • Kenton Varda's avatar
      Work around Clang bug 22354. · b0599220
      Kenton Varda authored
      https://llvm.org/bugs/show_bug.cgi?id=22354
      
      At the time DisallowConstCopy was introduced, GCC 4.7 and Clang 3.2 refused to allow the non-const copy constructors to be defaulted inline. This must have been concluded to be a compiler bug, as GCC 4.8 and Clang 3.4 seem fine with it. So, we can clean this up.
      
      Meanwhile, the above-linked Clang bug triggered when a DisallowConstCopy derivative is captured by value in a C++14 generic lambda. capnp::CallContext in particular tended to be hit by this a lot. The bug only affects non-default (or out-of-line default) copy constructors, and thus is conveniently sidestepped by this change.
      b0599220
  29. 20 Apr, 2015 2 commits