rust-lang.github.io to rustc-dev-guide.rust-lang.org

Author: chrissimpkins

content/_index.md

@@ -9,14 +9,14 @@ other such things. If you're interested in learning about how
 **rustc** works -- as well as advice on building the compiler, preparing a PR,
 and other similar topics -- check out the [rustc-dev-guide].
 
-[rustc-dev-guide]: https://rust-lang.github.io/rustc-dev-guide/
+[rustc-dev-guide]: https://rustc-dev-guide.rust-lang.org/
 
 ## Quick facts
 
 - **Where to find us:** We are primarily present on [Zulip](about/chat-platform), though some of us also monitor Discord.
 - **Want to attend a meeting or follow along?** See the "meeting calendar" section below.
 - **Looking for technical information about how the compiler works?**
-  Check out the [rustc-dev-guide](https://rust-lang.github.io/rustc-dev-guide/).
+  Check out the [rustc-dev-guide](https://rustc-dev-guide.rust-lang.org/).
 
 ## Meeting Calendar
 

content/minutes/design-meeting/2019-10-11-DepGraph-persistence-PR62038.md

@@ -13,7 +13,7 @@ Dear @*T-compiler/meeting*,
 
 Today we will be having a **design meeting**. The topic was originally sketched as "some Zoxc PR". We've since narrowed that down to discuss #62038, which is a refactoring to how dep-graph loading occurs. @**Zoxc** [wrote up a comment](https://github.com/rust-lang/rust/pull/62038#issuecomment-540508308) giving a summary of the ideas. Note that this PR itself is an incremental step towards #60035, which aims to make dep-graph loading/saving more continuous.
 
-I'd also like to discuss briefly how we should document these changes. We currently have some rustc-chapters on incremental compilation (e.g., [this chapter goes into detail](https://rust-lang.github.io/rustc-dev-guide/queries/incremental-compilation-in-detail.html)). I would like to move us to a world where major refactorings like #60035 (but not limited to this one -- I think e.g. [my recent PR](https://github.com/rust-lang/rust/pull/65232) and work on lazy norm fits the bill) come along with a rustc-dev-guide chapter that documents the new state of the world. Maybe we discuss some how that might work and -- in the case of THIS PR -- who might do that documentation work (I don't necessarily think it has to be @**Zoxc**, though they're also an obvious candidate). (In my ideal world, drafts of that chapter would be available *before* the PR, but at minimum I think such a chapter should be in place to help with reviewing.)
+I'd also like to discuss briefly how we should document these changes. We currently have some rustc-chapters on incremental compilation (e.g., [this chapter goes into detail](https://rustc-dev-guide.rust-lang.org/queries/incremental-compilation-in-detail.html)). I would like to move us to a world where major refactorings like #60035 (but not limited to this one -- I think e.g. [my recent PR](https://github.com/rust-lang/rust/pull/65232) and work on lazy norm fits the bill) come along with a rustc-dev-guide chapter that documents the new state of the world. Maybe we discuss some how that might work and -- in the case of THIS PR -- who might do that documentation work (I don't necessarily think it has to be @**Zoxc**, though they're also an obvious candidate). (In my ideal world, drafts of that chapter would be available *before* the PR, but at minimum I think such a chapter should be in place to help with reviewing.)
 
 ## Questions for discussion
 

content/minutes/triage-meeting/2019-10-10.md

@@ -39,7 +39,7 @@ type: docs
 
 ### [wg-learning](https://rust-lang.github.io/compiler-team/working-groups/learning/)
 
-- `wg-learning` has been working on transcribing videos from the [compiler lecture series](https://www.youtube.com/watch?v=elBxMRSNYr4&list=PL85XCvVPmGQhOL-J2Ng7qlPvDVOwYpGTN) into [rustc-dev-guide](https://rust-lang.github.io/rustc-dev-guide/) chapters.
+- `wg-learning` has been working on transcribing videos from the [compiler lecture series](https://www.youtube.com/watch?v=elBxMRSNYr4&list=PL85XCvVPmGQhOL-J2Ng7qlPvDVOwYpGTN) into [rustc-dev-guide](https://rustc-dev-guide.rust-lang.org/) chapters.
 
 - Originally, individuals were assigned one or lectures to complete but that hasn't worked very well.
 

content/minutes/triage-meeting/2019-10-17.md

@@ -52,9 +52,9 @@ type: docs
 
 - The [Inside Rust](https://blog.rust-lang.org/inside-rust/index.html) blog has launched.
 
-- The [ICE-Breaker group](https://rust-lang.github.io/rustc-dev-guide/ice-breaker/about.html) has been formed!
+- The [ICE-Breaker group](https://rustc-dev-guide.rust-lang.org/ice-breaker/about.html) has been formed!
 
-- The [LLVM ICE-Breaker group](https://rust-lang.github.io/rustc-dev-guide/ice-breaker/llvm.html) is also being formed.
+- The [LLVM ICE-Breaker group](https://rustc-dev-guide.rust-lang.org/ice-breaker/llvm.html) is also being formed.
 
 [Link to full conversation](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/weekly.20meeting.202019-10-17.20.2354818/near/178389266)
 

content/working-groups/learning/minutes/2019.10.01-meeting.md

@@ -8,7 +8,7 @@ type: docs
   - Everyone is [taking notes in this paper doc](https://paper.dropbox.com/doc/Ty-lecture-summary--AlwygwSe9rh1NVn2BB6CaBB9Ag-4jFj9bVOLlW7uhIOWHITX).
   - Discussion was about this lecture https://github.com/rust-lang/rustc-dev-guide/issues/375
 
-- @Santiago Pastorino reported that [How to build and run guide page needs help](https://rust-lang.github.io/rustc-dev-guide/how-to-build-and-run.html)
+- @Santiago Pastorino reported that [How to build and run guide page needs help](https://rustc-dev-guide.rust-lang.org/how-to-build-and-run.html)
   - Team might create a new doc for this page to collect ideas.
 
 - @mark-i-m reported that 

content/working-groups/llvm/_index.md

@@ -66,5 +66,5 @@ something to do with how LLVM works. For the time being this is the best place t
 [Code Reviews with Phabricator]: https://llvm.org/docs/Phabricator.html
 [Getting Started with the LLVM System]: https://www.llvm.org/docs/GettingStarted.html
 [Intro to LLVM]: http://www.aosabook.org/en/llvm.html
-[codegen section]: https://rust-lang.github.io/rustc-dev-guide/codegen.html
-[rustc-dev-guide]: https://rust-lang.github.io/rustc-dev-guide/
+[codegen section]: https://rustc-dev-guide.rust-lang.org/codegen.html
+[rustc-dev-guide]: https://rustc-dev-guide.rust-lang.org/

content/working-groups/mir-opt/_index.md

@@ -43,7 +43,7 @@ and context:
 
 - MIR is an intermediate representation used within the compiler. We are looking to transform
   instances of MIR into "better" instances. You can read about the MIR in
-  the [relevant rustc-dev-guide chapter](https://rust-lang.github.io/rustc-dev-guide/mir/index.html).
+  the [relevant rustc-dev-guide chapter](https://rustc-dev-guide.rust-lang.org/mir/index.html).
 
 ## Do I need to attend any meetings?
 We don't have any meetings yet.

content/working-groups/nll/_index.md

@@ -53,9 +53,9 @@ and context:
 
 - MIR is an intermediate representation used within the compiler. NLL is implemented as a new
   borrow checker implemented on the MIR. You can read about the MIR in
-  the [relevant rustc-dev-guide chapter](https://rust-lang.github.io/rustc-dev-guide/mir/index.html).
+  the [relevant rustc-dev-guide chapter](https://rustc-dev-guide.rust-lang.org/mir/index.html).
 - You can read about the major phases and internals of the MIR borrow checker in
-  it's [rustc-dev-guide chapter](https://rust-lang.github.io/rustc-dev-guide/borrow_check.html).
+  it's [rustc-dev-guide chapter](https://rustc-dev-guide.rust-lang.org/borrow_check.html).
 - NLL was originally specified
   in [RFC 2094](https://github.com/rust-lang/rfcs/blob/master/text/2094-nll.md).
 - [@nikomatsakis][nikomatsakis]'s blog posts on NLL are also useful for getting familiar with the

content/working-groups/parallel-rustc/_index.md

@@ -23,7 +23,7 @@ This working group aims to accomplish the following:
 - Produce solid documentation of how parallel evaluation works, how it is
   implementated, and what things it might affect in the [rustc-dev-guide][rustc-dev-guide].
 
-[rustc-dev-guide]: https://rust-lang.github.io/rustc-dev-guide/
+[rustc-dev-guide]: https://rustc-dev-guide.rust-lang.org/
 
 # How can I get involved?
 If you are interested in getting involved in this working group, you are welcome to

content/working-groups/rfc-2229/_index.md

@@ -72,7 +72,7 @@ The project roadmap can be found [here][roadmap].
 
 [Niko]: https://github.com/nikomatsakis
 [Blitzerr]: https://github.com/blitzerr
-[rustc-dev-guide]: https://rust-lang.github.io/rustc-dev-guide/
+[rustc-dev-guide]: https://rustc-dev-guide.rust-lang.org/
 [repo]: https://github.com/rust-lang/rust
 [zulip]: https://rust-lang.zulipchat.com/#narrow/stream/189812-t-compiler.2Fwg-rfc-2229
 [RFC-2229]: https://github.com/rust-lang/rfcs/blob/master/text/2229-capture-disjoint-fields.md

content/working-groups/template/_index.md

@@ -51,9 +51,9 @@ and context:
 
 - MIR is an intermediate representation used within the compiler. NLL is implemented as a new
   borrow checker implemented on the MIR. You can read about the MIR in
-  the [relevant rustc-dev-guide chapter](https://rust-lang.github.io/rustc-dev-guide/mir/index.html).
+  the [relevant rustc-dev-guide chapter](https://rustc-dev-guide.rust-lang.org/mir/index.html).
 - You can read about the major phases and internals of the MIR borrow checker in
-  it's [rustc-dev-guide chapter](https://rust-lang.github.io/rustc-dev-guide/borrow_check.html).
+  it's [rustc-dev-guide chapter](https://rustc-dev-guide.rust-lang.org/borrow_check.html).
 - NLL was originally specified
   in [RFC 2094](https://github.com/rust-lang/rfcs/blob/master/text/2094-nll.md).
 - [@nikomatsakis][nikomatsakis]'s blog posts on NLL are also useful for getting familiar with the