FLS scope
Nobody has claimed this yet.
- Dominant language
- reStructuredText
- Stars
- 497
- Forks
- 41
- Avg merge
- 3h 52m
- Merged PRs (30d)
- 4
Description
When the FLS was first written, only the alloc and core libraries were in scope. This was intentional, as alloc and core are OS-agnostic, and are very tightly coupled with the language semantics. std is another story.
We can either keep it the same way but start writing down somewhere which std-related items were not included in the FLS (in case we want to include them later), or start introducing std items into the FLS.
I think this needs a higher level discussion.
Originally posted by @kirtchev-adacore in https://github.com/rust-lang/fls/pull/698#discussion_r3135986480
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 with the discussion linked from rust-lang/fls#698 and read the scope described in this issue. Determine whether std-related items should remain out of the FLS or be added, and record the decision and any exclusions in the appropriate FLS documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100