Using return_value_policy::copy for non-copyable type
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7
- Forks
- 3
- Avg merge
- 18h 33m
- Merged PRs (30d)
- 7
Description
InitSendable (see https://github.com/robotpy/robotpy-commands-v2/pull/22 for example) takes a non-copyable type as an argument. Since the smart-holder branch of pybind11 can invalidate objects, we might be able to automatically detect and fix this case at compile time. Would need some thought.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing InitSendable and the example in robotpy-commands-v2 pull request #22, then inspect how the smart-holder branch of pybind11 handles invalidation and return_value_policy::copy. Determine whether non-copyable arguments can be detected at compile time and define the expected automatic fix; the issue is complete only when that behavior is specified and implemented with appropriate coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100