P3019R14 `indirect` And `polymorphic`: Vocabulary Types For Composite Class Design
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 11.1k
- Forks
- 1.7k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 22
Description
WG21-P3019R14 indirect And polymorphic: Vocabulary Types For Composite Class Design
LWG-4251 Move assignment for indirect unnecessarily requires copy construction
LWG-4325 std::indirect's operator== still does not support incomplete types
LWG-4532 Imprecise std::polymorphic wording seems to imply slicing
Feature-test macro:
#define __cpp_lib_indirect 202502L
#define __cpp_lib_polymorphic 202502L
Note: We are not yet accepting PRs for C++26 features.
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 by reading WG21-P3019R14 and the three listed LWG issues to understand the proposed indirect and polymorphic vocabulary types and their wording requirements. The issue notes that PRs for C++26 features are not yet accepted; completion would require an implementation and the specified __cpp_lib_indirect and __cpp_lib_polymorphic feature-test macros.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100