Issue: object ref-count ignored when moving std::unique_ptr #2906
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.
Inspecting the unit tests of #2904 in more detail, I noticed that the smart holder code is actually ignoring an object's ref-count, although there is this test:
pybind11/include/pybind11/detail/smart_holder_type_casters.h
Line 380 in 784092d
Nevertheless, as shown in this example, the refcount of the object before
moving
it, is 3! Something weird is going on there. Moving should fail in this case, shouldn't it? @rwgkHaving that said, I actually want to have the possibility to move an object with a refcount > 1. Otherwise, I couldn't move a variable, but only "rvalues". There are extra checks in place to ensure that I don't access a disowned object again...