[BUG]: pass parameters by const reference
Open
Nobody has claimed this yet.
triage
- Dominant language
- C++
- Stars
- 18k
- Forks
- 2.3k
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 10
Description
Required prerequisites
- Make sure you've read the documentation. Your issue may be addressed there.
- Search the issue tracker and Discussions to verify that this hasn't already been reported. +1 or comment there if it has.
- Consider asking first in the Gitter chat room or in a Discussion.
What version (or hash if on master) of pybind11 are you using?
pybind11/2.6.1
Problem description
when i pass a const reference from python to a c++ class, the m_ptr will be null later
Reproducible example code
class A {
const pybind11::array_t<int64_t>& data;
A(const pybind11::array_t<int64_t> data): data(data){}
}
can not work, while remove the const it is fine
class A {
pybind11::array_t<int64_t> data;
A(const pybind11::array_t<int64_t> data): data(data){}
}
Is this a regression? Put the last known working version here if it is.
Not a regression
Contributor guide
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
The payload names no repository files or tests. Start by reproducing the pybind11 2.6.1 example with class A, comparing the const-reference member with the value member and observing when m_ptr becomes null. Done should establish the expected lifetime behavior and record the result in an appropriate regression test or issue clarification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100