Book should say what it is about #3767
Conversation
ehuss
added
the
not-rfc
| This book is a collection of all RFCs that have been accepted. | ||
|
|
||
| The "RFC" (request for comments) process is intended to provide a consistent | ||
| and controlled path for changes to Rust (such as new features) so that all | ||
| stakeholders can be confident about the direction of the project. |
There was a problem hiding this comment.
Probably the bit being added would make more sense as the second paragraph, after the nature of an RFC has been introduced.
There was a problem hiding this comment.
No, I don't think that is right. The very first thing this book should say is what it is about at the highest level possible. Then the details of that thing can be explained later.
Also to be able to understand """The "RFC" process ... the direction of the project.""" it helps greatly if you already know what this book is about.
|
I see there are some confused emojis, so I will try to explain a bit more. Currently I am unsure whether this book is a collection of RFCs that:
Does the book explain this somewhere and I missed it? Which of these options is correct? |
This is my best guess at what this book is, but I could be wrong, since this does not seem to be stated anywhere...