Ryan Levick
Ryan Levick
In the guide on [hir](https://rustc-dev-guide.rust-lang.org/hir.html), the terms "definition", "node", and "item" are used without much explanation which leaves the terms vague and fuzzy. If possible, we should try to more...
The guide is filled with lots of todos. We should ensure that these todos are relevant, have issues, and that the todos references there issues directly in the text.
In the section on AST to HIR [lowering](https://rustc-dev-guide.rust-lang.org/lowering.html), these terms are used without explanation or definition. Perhaps they should be added to the glossary and then linked to.
In the section on AST to HIR [lowering](https://rustc-dev-guide.rust-lang.org/lowering.html), the `DefCollector` is mentioned without explanation. We should talk more about what it is.
In the section on AST to HIR [lowering](https://rustc-dev-guide.rust-lang.org/lowering.html), there is no mention of where lowering actually takes place or what mechanisms are used to perfom lowering.
When parsing identifiers, `accept_as_ident` is used to reject those strings which are keywords. This does not include Rust 2018 keywords such as `async` and `try`. Additionally, the linked resource for...
Thanks for the awesome crate! 🎉 For the [WinRT crate](https://github.com/microsoft/winrt-rs) we generate _a lot_ of code, and so performance is a concern. We noticed that when using the `quote!` macro...
This is an RFC for how we'll handle the many types of Strings in Rust and Windows and how they interact with each other. This is a complicated question, so...
Using a tool lime TryBuild we can test that certain code does not build and that the diagnostics the end user gets are what we expect.
We now have support for unrolling a rollup and building artifacts for them. The shas identifying these artifacts are then posted to GitHub, but they are not stored anywhere else....