Issues on the RFCs and Rust repos


We are changing where to file issues a little bit. From now on, issues should only be filed on the Rust repo for implementation issues, bugs, or meta-issues. Issues which deal with language design or are major changes to the libraries or are feature requests should be filed on the RFCs repo. In short, anything that would require an RFC before implementation should be on the RFCs repo.

At some point in the next few days I will transfer any existing issues that are RFC-like from the Rust repo to the RFCs repo. All comments will be preserved.

Please note that filing an issue on the RFCs repo is not a substitute for a proper RFC as a PR. Ideas for change to Rust are only likely to get serious attention if there is an RFC. The motivation for issues on the RFCs repo is so that we can track feature requests etc. before they are ready for a RFC.

Thanks, Nick.



So just to clarify: All issues of the form “add/implement X” should now be submitted to the RFCs repo? I was under the impression that many actions of this form specifically did not require an RFC, is that changing?

Will these changes be documented in any more concrete way? Just want to be sure I understand.



Nothing is changing as to which changes need an RFC. A change needs an RFC today if and only if it did yesterday.

If X is a non-major library change it should still go to the Rust repo. If X is a language feature of a major change to the libraries it should go to RFCs.

I hope this is concrete enough, let me know if I can clarify further.



The transfer of issues has happened. If you find RFC-like issues in the Rust repo please move them to the RFCs repo, or ping me and I can do it.


closed #5

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.