`<complex>`: Do we still want `_Ctraits`?
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C++
- Stars
- 11.1k
- Forks
- 1.7k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 22
Description
It seems that <complex> can be made a bit clearer if we remove _Ctraits and some other outdated internal dispatching mechanisms. However, it is unclear whether _Ctraits is an intentional customization mechanism.
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 locating the implementation and reading _Ctraits alongside the other outdated internal dispatching mechanisms it uses. Determine whether _Ctraits is intended as a customization mechanism; done requires a settled decision on whether it and the related mechanisms should be removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100