Create issues for many TODOs (#1163)

* Create issues for many TODOs

* Update src/crates-io.md

Co-authored-by: Joshua Nelson <[email protected]>

* Update src/backend/inline-asm.md

Co-authored-by: Yuki Okushi <[email protected]>

Co-authored-by: Joshua Nelson <[email protected]>
Co-authored-by: Yuki Okushi <[email protected]>

Author: 3 people

src/ast-validation.md

@@ -3,4 +3,4 @@
 AST validation is the process of checking various correctness properties about
 the AST after macro expansion.
 
-**TODO**: write this chapter.
+**TODO**: write this chapter. [#656](https://github.com/rust-lang/rustc-dev-guide/issues/656)

src/backend/inline-asm.md

@@ -1,4 +1,5 @@
 # Inline Assembly
 
-**TODO: You can find more info in
-https://github.com/rust-lang/rust/pull/69171#issue-375572066**
+**TODO**: You can find more info 
+[here](https://github.com/rust-lang/rust/pull/69171#issue-375572066)
+[#1162](https://github.com/rust-lang/rustc-dev-guide/issues/1162)

src/crates-io.md

@@ -12,7 +12,9 @@ reasons:
 - The dependency may have transitive dependencies that have one of the above
   problems.
 
-TODO: what is the vetting process?
+As of <!-- date: 2021-07 --> July 2021, there is no official policy for vetting
+new dependencies to the compiler. Generally, new dependencies are not added 
+to the compiler unless there is a good reason to do so.
 
 ## Permitted dependencies
 

src/debugging-support-in-rustc.md

@@ -314,8 +314,7 @@ Clang always embeds an MD5 checksum, though this does not appear in documentatio
 * New demangler in `libiberty` (gcc source tree).
 * New demangler in LLVM or LLDB.
 
-**TODO**: Check the location of the demangler source.
-[Question on Github](https://github.com/rust-lang/rustc-dev-guide/pull/316#discussion_r283062536).
+**TODO**: Check the location of the demangler source. [#1157](https://github.com/rust-lang/rustc-dev-guide/issues/1157)
 
 #### Reuse Rust compiler for expressions
 

src/feature-gate-ck.md

@@ -1,3 +1,3 @@
 # Feature Gate Checking
 
-**TODO**: this chapter
+**TODO**: this chapter [#1158](https://github.com/rust-lang/rustc-dev-guide/issues/1158)

src/hir-debugging.md

@@ -5,4 +5,4 @@ The `-Z unpretty=hir-tree` flag will dump out the HIR.
 If you are trying to correlate `NodeId`s or `DefId`s with source code, the
 `--pretty expanded,identified` flag may be useful.
 
-TODO: anything else?
+TODO: anything else? [#1159](https://github.com/rust-lang/rustc-dev-guide/issues/1159)

src/identifiers.md

@@ -82,7 +82,7 @@ See the [HIR chapter][hir-map] for more detailed information.
 - [`Promoted`] identifies a promoted constant within another item (related to
   const evaluation). Note: it is unique only locally within the item, so it
   should be associated with a `DefId`.
-  [`GlobalId`] will give you a more specific identifier (TODO).
+  [`GlobalId`] will give you a more specific identifier.
 
 - [`GlobalId`] identifies a global variable: a `const`, a `static`, a `const fn`
   where all arguments are [zero-sized types], or a promoted constant.

src/macro-expansion.md

@@ -608,10 +608,10 @@ Because the Rust ABI is unstable, we use the C ABI for this conversion.
 [pm]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_expand/proc_macro/index.html
 [pms]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_expand/proc_macro_server/index.html
 
-TODO: more here.
+TODO: more here. [#1160](https://github.com/rust-lang/rustc-dev-guide/issues/1160)
 
 ### Custom Derive
 
 Custom derives are a special type of proc macro.
 
-TODO: more?
+TODO: more? [#1160](https://github.com/rust-lang/rustc-dev-guide/issues/1160)

src/name-resolution.md

@@ -164,7 +164,7 @@ To tell the difference between speculative loads and loads initiated by the
 user, resolve passes around a `record_used` parameter, which is `false` when
 the load is speculative.
 
-## TODO:
+## TODO: [#16](https://github.com/rust-lang/rustc-dev-guide/issues/16)
 
 This is a result of the first pass of learning the code. It is definitely
 incomplete and not detailed enough. It also might be inaccurate in places.

src/type-checking.md

@@ -41,4 +41,4 @@ For more details, see the [`collect`][collect] module.
 [queries]: ./query.md
 [collect]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_typeck/collect/
 
-**TODO**: actually talk about type checking...
+**TODO**: actually talk about type checking... [#1161](https://github.com/rust-lang/rustc-dev-guide/issues/1161)