Closing issues relevant to T-lang on this repo
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
My understanding is that T-lang is not interested in following discussion on the RFCs repo that is not actual RFC. Various proposals seem interesting but are unfortunately in the form of issues instead of RFCs. If someone wanted to pursue them as an RFC, they should open it as a PR (following the template where useful, as usual).
@rust-lang/lang I would like to ask that you formally FCP that
- the language team is not going to (formally) take suggestions from GitHub issues on the RFCs repo
- thus T-lang will not act on these GitHub issues as change proposals
- thus that all GitHub issues that are relevant to T-lang on this repo can simply be closed, with a directive to open an RFC or to pursue some other process, as appropriate
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
Review issue #3756 and its 19-comment discussion about how the RFCs repository handles GitHub issues relevant to T-lang. No specific file or test is named; completion would require a formal language-team decision, guidance to open an RFC or use another process, and closure of applicable issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100