Source encoding
Nobody has claimed this yet.
- Dominant language
- reStructuredText
- Stars
- 497
- Forks
- 41
- Avg merge
- 3h 52m
- Merged PRs (30d)
- 4
Description
§2.1:17 (fls_2brw13n9ldgy) reads
The coded representation of a character is tool-defined.
As I understand it, the aim of the FLS is currently understood to be to model the behaviour of one particular version of rustc, not to define more general rules for implementations of Rust.
If that's right, I think this paragraph should instead be saying that the representation is always UTF-8.
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
Locate §2.1:17, identified as fls_2brw13n9ldgy, and read the surrounding specification text first. Confirm whether the FLS is intended to model rustc behavior, then update this passage so the character representation is stated as UTF-8; done when the section clearly reflects the intended rule.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100