P1673: Should sqrt be a customization point?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 29
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
@crtrott This issue addresses the remaining P1673 points in #281.
- Specify whether we are using
std::sqrt(or::sqrt) (important, because it has user-visible side effects likeerrno). - Is
sqrta customization point, likeabsandconjare? If so, add it to front matter.
The second point asks whether P1673 should make sqrt a customization point, just like conj-if-needed. sqrt has the problem that it turns integral arguments into double. Thus, it has type preservation issues analogous to conj. However, unlike conj, we can't trivially fix sqrt for integral arguments.
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 reading the remaining P1673 points referenced from #281 and the surrounding proposal text. Resolve whether sqrt uses std::sqrt or ::sqrt and whether it is a customization point; done means the decision is documented and the relevant front matter is updated if needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100