Document and establish compatibility guidelines for Unicode version used
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Friday Dec 12, 2014 at 02:07 GMT
For earlier discussion, see https://github.com/rust-lang/rust/issues/19762
This issue was labelled with: A-collections, A-libs in the Rust repository
We already have unicode::char::UNICODE_VERSION, but we need to guarantee that:
- Newer version of Rust can only update to the newer version of Unicode standard (see also the Unicode character encoding stability policy); and
- Such update only occurs on the minor version or major version.
In addition, we may want to document that some #[stable] methods or functions can change its behavior in the backward compatible fashion: trim is one example (depends on the White_Space property). This is a rationale for the item 2 above.
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 earlier discussion in issue 19762 and the linked Unicode character encoding stability policy, then inspect the existing unicode::char::UNICODE_VERSION context. Done means an agreed, documented compatibility and versioning guideline covering Unicode updates and behavior changes such as trim.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation, internationalization
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100