-
Notifications
You must be signed in to change notification settings - Fork 1.6k
A "Design FAQ" document #615
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
Comments
I liked having a complete list of the questions on one web page (as I noted in my comment on the original issue) I suggest we either:
In the meantime I am planning to continue writing my comments in rust-lang/rust#4047 (even though it is closed) , since for the short term, that is the easiest way to keep all of the proposed questions in one place. (I suggest others do the same until we decide on some other way to resolve this problem.) |
quick decision: I will try to import the comments from rust-lang/rust#4047 in the near term. |
I could move this over without the `--ignore-comments` flag and it would
just move all the comments over?
|
That didn't work (#891) due to rate limiting. |
I believe https://www.rust-lang.org/en-US/faq.html satisfies this "Design FAQ" document idea. So I'm closing this as being completed. |
Tuesday Nov 27, 2012 at 20:34 GMT
For earlier discussion, see rust-lang/rust#4047
This issue was labelled with: A-docs, I-wishlist in the Rust repository
In the vein of the Project FAQ and the Language FAQ.
In addition to being really interesting, this would save a lot of time and divert a lot of potential questions in the long run. Some topics to discuss:
(see e.g. rust-dev post.)
Explanations should be technical and include code examples wherever possible.
Some of the questions of this nature overlap with the latter half of the Language FAQ, but not all, e.g. "Can Rust code call C code?" and "What is the difference between a managed pointer and an owned pointer?" do not belong. The document should focus on large-scale design decisions and tradeoffs; think "Why split stacks?" rather than "How do split stacks work?".
If you think of good questions, add them in the comments here. There are probably a lot of ripe areas for explanation, especially with regard to mutability and regions.
The text was updated successfully, but these errors were encountered: