1. 05 Aug, 2020 1 commit
  2. 02 Aug, 2020 1 commit
  3. 31 Jul, 2020 1 commit
  4. 29 Jul, 2020 4 commits
  5. 19 Jul, 2020 2 commits
  6. 13 Jul, 2020 1 commit
  7. 11 Jul, 2020 4 commits
  8. 10 Jul, 2020 1 commit
    • Jeff Trull's avatar
      Improve build times through header removal and relocation · 3438f227
      Jeff Trull authored
      - Eliminate unused headers
      - reduce dependencies among headers (slightly)
      
      The include-what-you-use tool (IWYU) was used to analyze header
      dependencies and recommend fixes; some additional manual work was
      then performed.
      
      Add missing include
      3438f227
  9. 09 Jul, 2020 1 commit
  10. 08 Jul, 2020 2 commits
  11. 07 Jul, 2020 1 commit
    • Jeff Trull's avatar
      Mass conversion of bind() calls to lambdas · 4c3b87a8
      Jeff Trull authored
      Source file work done with custom-modified versions of clang-format
      and clang-tidy, via the modernize-avoid-bind checker. Headers were
      modified by hand. A script removed uses of <functional> and <boost/bind.hpp>.
      4c3b87a8
  12. 02 Jul, 2020 1 commit
  13. 25 Jun, 2020 4 commits
  14. 08 Jun, 2020 1 commit
  15. 06 Jun, 2020 3 commits
    • Jeff Trull's avatar
      8ba30ef3
    • Jeff Trull's avatar
      Remove boost::any wrapper around std::shared_ptr · 4c8a80b5
      Jeff Trull authored
      std::shared_ptr provides a limited amount of type erasure natively
      based on void* and the fact that it stores the original type in the
      deleter. As a result, if you know the original type, you can call
      std::static_pointer_cast and recover a legitimate shared_ptr of the
      right type, very efficiently.
      
      It looks like the use of boost::any in this code is:
      
      1) to hide the pointed-to type so a uniform container can be used
      2) to represent "no pointer"
      
      both of which can be handled natively by shared_ptr<void> with a small
      performance gain from removing one indirection.
      4c8a80b5
    • Jeff Trull's avatar
      Remove const qualifier from object that can be modified · ac746100
      Jeff Trull authored
      Modifying an object declared const is technically undefined behavior,
      and compilers are entitled to do as they like with such code. The most
      likely result - in the event of some future optimizer - would be
      elimination of the code performing the modification, although it could
      theoretically be anything.
      
      Given that ConstantPropertyMap defines an assignment operator already,
      simply changing the underlying data member to non-const (while making
      it private) seems to achieve the same result as the current code while
      avoiding UB.
      ac746100
  16. 05 Jun, 2020 2 commits
  17. 02 Jun, 2020 3 commits
  18. 29 May, 2020 2 commits
  19. 28 May, 2020 5 commits