Make unique_ptr's with non-default deleters work #384
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently pybind11 only supports
std::unique_ptr<T>
holders by default (other holders can, of course, be declared using the macro). PR #368 added apy::nodelete
that is intended to be used as:but this doesn't work out of the box. (You could add an explicit holder type declaration, but this doesn't appear to have been the intention of the commit).
This commit fixes it by generalizing the
unique_ptr
type caster to take both the type and deleter as template arguments, so that any unique_ptr types are now automatically handled by pybind (not justpy::nodelete
). It also adds a test to test_smart_ptr, testing both thatpy::nodelete
(now) works, and that thepy::nodelete
-managed object is indeed not deleted as intended.