[FEAT] Should teach `py::type::of<>` to handle non-generic types
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 18k
- Forks
- 2.3k
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 10
Description
See discussions in #2364:
- https://github.com/pybind/pybind11/pull/2364#issuecomment-690744846
- https://github.com/pybind/pybind11/pull/2364#issuecomment-691575432
- https://github.com/pybind/pybind11/pull/2364#issuecomment-692084568
FYI @YannickJadoul @henryiii - Im' filing this pre-emptively ;) Feel free to close this as part of #2364 if y'all incorporate it in that PR.
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
Start with the py::type::of<> entry point and read the discussions linked from #2364, especially the three referenced pull-request comments. No files or tests are named; first establish the intended behavior for non-generic types, then identify the relevant implementation and verification points. Done means py::type::of<> supports the agreed non-generic cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100