Add note to [re.traits] about non-standard character classes are allowed
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
With the acceptance of LWG DR 2018 the spec for isctype still doesn't allow for additional implementation-defined character classes, because "the result is
determined as if by ..." doesn't allow for handling additional special
cases similar to how underscores are handled.
A note on isctype saying "implementations are permitted to support additional character classes recognized by lookup_classname()" might be enough, given that lookup_classname() has normative wording saying "at least" the named classes will be recognized.
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 with the [re.traits] wording for isctype and lookup_classname(), focusing on the proposed note and the existing “at least” language. Add wording that permits additional implementation-defined character classes, then verify that the surrounding normative text remains consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100