Book should say what it is about
This is my best guess at what this book is, but I could be wrong, since this does not seem to be stated anywhere...
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:
- have merely been written
- have also had some review for clarity and consistency
- have also had some review for desirability of implementation
- have also been implemented (I'm pretty sure it's not this one, but it's not stated anywhere AFAIK)
- a combination of all previous categories
Does the book explain this somewhere and I missed it? Which of these options is correct?
What the process is says: """ In short, to get a major feature added to Rust, one must first get the RFC merged into the RFC repository as a markdown file. At that point the RFC is “active” and may be implemented with the goal of eventual inclusion into Rust. """
We discussed this pull request during @rust-lang/internal-sites triage of non-RFC PRs in #t-internal-sites > Stale non-RFC PRs @ 💬.
We consider that adding the proposed sentence to the README is going to be confusing for visitors coming to the repository (where the new sentence doesn't make sense).
It is unfortunate that the README is shared between the book and the repository.
Thanks you for attempting to improve the book.
Feel free to open a new PR (or re-open this PR) with a better proposal.
@Urgau thanks for discussing this issue; perhaps I'll see if I can find a better place for this information.