-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TODO: Reference Manual: Rationales and design tradeoffs #2172
Comments
As with many things related to spec documents, I think the Ada rationale provides an excellent model for this: http://www.ada-auth.org/standards/12rat/html/Rat12-TOC.html -- but we can probably close this bug out simply by roughing the section out. All such docs are likely to grow endlessly. |
Visiting for triage. Still important. |
visit, triage email from 2013 sep 16. maybe this bug would be easier for individuals to tackle if we first wrote an outline of what specific topics this appendix should cover, and then filed bugs for each of them? I would not want to attempt to write this section on my own in one go... |
I think this is probably the same issue as #4047 |
http://doc.rust-lang.org/complement-design-faq.html <- this issue can be closed. |
Closing as a dupe of #4047. |
Found a TODO in the reference manual without a corresponding issue on file:
http://doc.rust-lang.org/doc/rust.html#appendix-rationales-and-design-tradeoffs
Filed for completeness, but also this would be really fascinating to read!
The text was updated successfully, but these errors were encountered: