1.7 KiB
- Feature Name: (fill me in with a unique ident, my_awesome_feature)
- Start Date: (fill me in with today's date, YYYY-MM-DD)
- RFC PR: (leave this empty)
- Rust Issue: (leave this empty)
Summary
One para explanation of the feature.
Motivation
Why are we doing this? What use cases does it support? What is the expected outcome?
Detailed design
This is the bulk of the RFC. Explain the design in enough detail for somebody familiar with the language to understand, and for somebody familiar with the compiler to implement. This should get into specifics and corner-cases, and include examples of how the feature is used.
How We Teach This
What names and terminology work best for these concepts and why? How is this idea best presented—as a continuation of existing Rust patterns, or as a wholly new one?
Would the acceptance of this proposal change how Rust is taught to new users at any level? How should this feature be introduced and taught to existing Rust users?
What additions or changes to the Rust Reference, The Rust Programming Language, and/or Rust by Example does it entail?
What would an outline of a new section in the book look like? What should the reader be able to understand by the end of the section in the book?
What's an example that would show off this feature?
Drawbacks
Why should we not do this?
Alternatives
What other designs have been considered? What is the impact of not doing this?
Unresolved questions
What parts of the design are still TBD?