This repository was archived by the owner on Sep 30, 2020. It is now read-only.
Resolve a number of outstanding FAQ issues #905
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi @AndrewBrinker! Sorry this never got followed up on -- we don't have a great review process for the website. Want to rebase, then ping me for review? |
|
Alright, it should be ready to go now. @aturon |
| guiding it from a global perspective. There are also subteams to guide and foster development of particular areas of interest, including the core language, the compiler, Rust libraries, Rust tools, and moderation of the official Rust communities. Designs in each of these areas are advanced through an [RFC process](https://github.com/rust-lang/rfcs). For changes which do not require an RFC, decisions are made through pull requests on the [`rustc` repository](https://github.com/rust-lang/rust). | ||
| As far as [project governance](https://github.com/rust-lang/rfcs/blob/master/text/1068-rust-governance.md) goes, Rust is managed by a core team that sets the vision and priorities for the project, guiding it from a global perspective. There are also subteams to guide and foster development of particular areas of interest, including the core language, the compiler, Rust libraries, Rust tools, and moderation of the official Rust communities. Designs in each of these areas are advanced through an [RFC process](https://github.com/rust-lang/rfcs). For changes which do not require an RFC, decisions are made through pull requests on the [`rustc` repository](https://github.com/rust-lang/rust). | ||
|
|
||
| Long term planning is guided by a [yearly roadmap](https://github.com/brson/rfcs/blob/north-star/text/0000-north-star.md), with specific milestones set each year. |
There was a problem hiding this comment.
This should link to the merged RFC instead, which I believe is https://github.com/rust-lang/rfcs/blob/master/text/1728-north-star.md.
|
|
||
| <h3><a href="#why-has-rust-changed-so-much" name="why-has-rust-changed-so-much"> | ||
| Why has Rust changed so much over time? | ||
| </a></h3> | ||
|
|
||
| Rust started with a goal of creating a safe but usable systems programming language. In pursuit of this goal it explored a lot of ideas, some of which it kept (lifetimes, traits) while others were discarded (the typestate system, green threading). Also, in the run up to 1.0 a lot of the standard library was rewritten as early designs were updated to best use Rust's features and provide quality, consistent cross-platform APIs. Now that Rust has reached 1.0, the language is guaranteed to be "stable"; and while it may continue to evolve, code which works on current Rust should continue to work on future releases. | ||
| Rust started with a goal of creating a safe but usable systems programming language. In pursuit of this goal it explored a lot of ideas, some of which it kept (lifetimes, traits) while others were discarded (the typestate system, green threading). Also, in the run up to 1.0 a lot of the standard library was rewritten as early designs were updated to best use Rust's features and provide quality, consistent cross-platform APIs. Now that Rust has reached 1.0, the language is [guaranteed to be "stable"](https://blog.rust-lang.org/2014/10/30/Stability.html); and while it may continue to evolve, code which works on current Rust should continue to work on future releases. |
There was a problem hiding this comment.
Hm, I'm not sure about putting stable in quotes -- I think linking to the stability policy is good (but I think there's an RFC which covers this better? I wasn't able to quickly find it, but maybe it's https://github.com/rust-lang/rfcs/blob/master/text/1105-api-evolution.md? @aturon can probably help more here...)
|
@AndrewBrinker ping! Got anything to say about @Mark-Simulacrum 's comments? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This resolves a number of the items in #886. In particular:
“Is this project controlled by Mozilla?“
“In which projects is Mozilla using Rust?“
“What examples are there of large Rust projects?“
“How can I try Rust easily?”
“How do I get help with Rust issues?”
“Why has Rust changed so much over time?”
“How fast is Rust?“
“Why curly braces? Why can’t Rust’s syntax be like Haskell’s or Python’s?”
“What is ‘monomorphisation’?“
“What the deal with
unwrap()everywhere?“?should probably be mentioned.“How do I get an error when I try to run example code that uses the
try!macro?”try!(and of course?by extension) inside ofmainhas been accepted as an RFC. This should be mentioned.