1. 02 Jul, 2020 5 commits
  2. 26 Jun, 2020 6 commits
  3. 25 Jun, 2020 9 commits
  4. 15 Jun, 2020 1 commit
  5. 14 Jun, 2020 1 commit
  6. 12 Jun, 2020 1 commit
  7. 09 Jun, 2020 3 commits
  8. 08 Jun, 2020 2 commits
  9. 07 Jun, 2020 1 commit
  10. 06 Jun, 2020 6 commits
    • Tiago Peixoto's avatar
      Merge branch 'simplify-shared-any' into 'master' · 463dfbb4
      Tiago Peixoto authored
      Remove boost::any wrapper around std::shared_ptr
      
      See merge request !28
      463dfbb4
    • Tiago Peixoto's avatar
      Merge branch 'UB-constness' into 'master' · 42e857bc
      Tiago Peixoto authored
      Remove const qualifier from object that can be modified
      
      See merge request !27
      42e857bc
    • 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
    • Tiago Peixoto's avatar
      Merge branch 'pythonedge-final' into 'master' · 46993132
      Tiago Peixoto authored
      Mark PythonEdge as "final" per clang-tidy
      
      See merge request !26
      46993132
    • 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
  11. 05 Jun, 2020 3 commits
  12. 02 Jun, 2020 2 commits