LWG-4487 Is member `is_steady` of a Cpp17Clock type required to be usable in constant expressions?
Open
Nobody has claimed this yet.
chrono
LWG
- Dominant language
- C++
- Stars
- 11.1k
- Forks
- 1.7k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 22
Description
LWG-4487 Is member is_steady of a Cpp17Clock type required to be usable in constant expressions?
It looks like we don't have to do anything here, but it would be best to make is_clock stricter (see how _Layout_mapping_alike is implemented).
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 the Cpp17Clock requirement and the existing is_clock and _Layout_mapping_alike implementations. Determine whether is_steady must be usable in constant expressions, then verify whether the stricter is_clock behavior is warranted and validate the result with the relevant existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100