1. 15 Nov, 2021 1 commit
    • [master] Wrong caching of overrides (#3465) · afdc09de
      * override: Fix wrong caching of the overrides
      
      There was a problem when the python type, which was stored in override
      cache for C++ functions, was destroyed and  the record wasn't removed from the
      override cache. Therefor, dangling pointer was stored there. Then when the
      memory was reused and new type was allocated at the given address and the
      method with the same name (as previously stored in the cache) was actually
      overridden in python, it would wrongly find it in the override cache for C++
      functions and therefor override from python wouldn't be called.
      The fix is to erase the type from the override cache when the type is destroyed.
      
      * test: Pass by const ref instead of by value (clang-tidy)
      
      * test: Rename classes and move to different files
      
      Rename the classes and files so they're no too generic. Also, better place to
      test the stuff is in test_virtual_functions.cpp/.py as we're basically testing
      the virtual functions/trampolines.
      
      * Add TODO for erasure code
      
      * [pre-commit.ci] auto fixes from pre-commit.com hooks
      
      for more information, see https://pre-commit.ci
      
      Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
      Trigve committed
  2. 14 Nov, 2021 1 commit
  3. 12 Nov, 2021 1 commit
  4. 10 Nov, 2021 1 commit
  5. 08 Nov, 2021 2 commits
  6. 07 Nov, 2021 1 commit
  7. 06 Nov, 2021 1 commit
  8. 01 Nov, 2021 2 commits
  9. 29 Oct, 2021 1 commit
    • feat: allow kw-only args after a py::args (#3402) · e7c9753f
      * Simply has_kw_only_args handling
      
      This simplifies tracking the number of kw-only args by instead tracking
      the number of positional arguments (which is really what we care about
      everywhere this is used).
      
      * Allow keyword-only arguments to follow py::args
      
      This removes the constraint that py::args has to be last (or
      second-last, with py::kwargs) and instead makes py::args imply
      py::kw_only for any remaining arguments, allowing you to bind a function
      that works the same way as a Python function such as:
      
          def f(a, *args, b):
              return a * b + sum(args)
      
          f(10, 1, 2, 3, b=20)  # == 206
      
      With this change, you can bind such a function using:
      
          m.def("f", [](int a, py::args args, int b) { /* ... */ },
              "a"_a, "b"_a);
      
      Or, to be more explicit about the keyword-only arguments:
      
          m.def("g", [](int a, py::args args, int b) { /* ... */ },
              "a"_a, py::kw_only{}, "b"_a);
      
      (The only difference between the two is that the latter will fail at
      binding time if the `kw_only{}` doesn't match the `py::args` position).
      
      This doesn't affect backwards compatibility at all because, currently,
      you can't have a py::args anywhere except the end/2nd-last.
      
      * Take args/kwargs by const lvalue ref
      
      Co-authored-by: Henry Schreiner <HenrySchreinerIII@gmail.com>
      
      Co-authored-by: Henry Schreiner <HenrySchreinerIII@gmail.com>
      Jason Rhinelander committed
  10. 27 Oct, 2021 4 commits
  11. 26 Oct, 2021 2 commits
    • fix: improve support for Python 3.11-dev (#3368) · e7e2c79f
      * ci: support Python 3.11-dev
      
      Also update 3.10 to final, better PyPy usage
      
      * fix: use PyFrame_GetCode on Python 3.9+
      
      * ci: some bitiness of pypy not supported on win
      
      * chore: update CMake support to 3.22rc1 to quiet warning
      
      * fix: use dev version of py to fix Py 3.11
      
      * tests: print proper Eigen version
      
      * ci: include pypy2, not sure why
      
      * ci: avoid running on Python 3.11 for now
      
      * ci: fix runs
      
      * ci: simpler PyPy usage, drop unmaintained scipy + pypy index
      
      * ci: only binary numpy, wait on pypy 3.8
      
      * refactor: address review
      Henry Schreiner committed
    • fix: the types for return_value_policy_override in optional_caster (#3376) · c2d3e220
      * fix: the types for return_value_policy_override in optional_caster
      
      `return_value_policy_override` was not being applied correctly in
      `optional_caster` in two ways:
      - The `is_lvalue_reference` condition referenced `T`, which was the
      `optional<T>` type parameter from the class, when it should have used `T_`,
      which was the parameter to the `cast` function. `T_` can potentially be a
      reference type, but `T` will never be.
      - The type parameter passed to `return_value_policy_override` should be
      `T::value_type`, not `T`. This matches the way that the other STL container
      type casters work.
      
      The result of these issues was that a method/property definition which used a
      `reference` or `reference_internal` return value policy would create a Python
      value that's bound by reference to a temporary C++ object, resulting in
      undefined behavior. For reasons that I was not able to figure out fully, it
      seems like this causes problems when using old versions of `boost::optional`,
      but not with recent versions of `boost::optional` or the `libstdc++`
      implementation of `std::optional`. The issue (that the override to
      `return_value_policy::move` is never being applied) is present for all
      implementations, it just seems like that somehow doesn't result in problems for
      the some implementation of `optional`. This change includes a regression type
      with a custom optional-like type which was able to reproduce the issue.
      
      Part of the issue with using the wrong types may have stemmed from the type
      variables `T` and `T_` having very similar names. This also changes the type
      variables in `optional_caster` to use slightly more descriptive names, which
      also more closely follow the naming convention used by the other STL casters.
      
      Fixes #3330
      
      * Fix clang-tidy complaints
      
      * Add missing NOLINT
      
      * Apply a couple more fixes
      
      * fix: support GCC 4.8
      
      * tests: avoid warning about unknown compiler for compilers missing C++17
      
      * Remove unneeded test module attribute
      
      * Change test enum to have more unique int values
      
      Co-authored-by: Aaron Gokaslan <skylion.aaron@gmail.com>
      Co-authored-by: Henry Schreiner <HenrySchreinerIII@gmail.com>
      Ryan Cahoon committed
  12. 25 Oct, 2021 2 commits
  13. 23 Oct, 2021 1 commit
  14. 22 Oct, 2021 2 commits
  15. 21 Oct, 2021 1 commit
  16. 19 Oct, 2021 1 commit
  17. 18 Oct, 2021 2 commits
  18. 11 Oct, 2021 3 commits
    • Correct options on Eigen::MappedSparseMatrix & adding MSVC C4127 suppression… · 7c580586
      Correct options on Eigen::MappedSparseMatrix & adding MSVC C4127 suppression around Eigen includes. (#3352)
      
      * Adding MSVC C4127 suppression around Eigen includes.
      
      * For MSVC 2015 only: also adding the C4127 suppression to test_eigen.cpp
      
      * Copying original change from PR #3343, with extra line breaks to not run past 99 columns (our desired but currently not enforced limit).
      Ralf W. Grosse-Kunstleve committed
    • [pre-commit.ci] pre-commit autoupdate (#3353) · 02c05573
      updates:
      - [github.com/PyCQA/flake8: 3.9.2 → 4.0.1](https://github.com/PyCQA/flake8/compare/3.9.2...4.0.1)
      
      Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
      pre-commit-ci[bot] committed
    • Fix make_key_iterator/make_value_iterator for prvalue iterators (#3348) · 8a7c266d
      * Add a test showing a flaw in make_key_iterator/make_value_iterator
      
      If the iterator dereference operator returns a value rather than a
      reference (and that pair also does not *contain* references),
      make_key_iterator and make_value_iterator will return a reference to a
      temporary, causing a segfault.
      
      * Fix make_key_iterator/make_value_iterator for prvalue iterators
      
      If an iterator returns a pair<T1, T2> rather than a reference to a pair
      or a pair of references, make_key_iterator and make_value_iterator would
      return a reference to a temporary, typically leading to a segfault. This
      is because the value category of member access to a prvalue is an
      xvalue, not a prvalue, so decltype produces an rvalue reference type.
      Fix the type calculation to handle this case.
      
      I also removed some decltype parentheses that weren't needed, either
      because the expression isn't one of the special cases for decltype or
      because decltype was only used for SFINAE. Hopefully that makes the code
      a bit more readable.
      
      Closes #3347
      
      * Attempt a workaround for nvcc
      Bruce Merry committed
  19. 09 Oct, 2021 1 commit
  20. 08 Oct, 2021 3 commits
  21. 04 Oct, 2021 7 commits