| Age | Commit message (Collapse) | Author | Lines |
|
|
|
|
|
See https://github.com/rust-lang/rustc-dev-guide/pull/1605#discussion_r1110388310
|
|
|
|
|
|
|
|
Co-authored-by: Noah Lev <camelidcamel@gmail.com>
|
|
See
- https://github.com/rust-lang/rustc-dev-guide/pull/1606#discussion_r1109298849
- https://github.com/rust-lang/rustc-dev-guide/pull/1606#discussion_r1109298280
|
|
|
|
|
|
They currently also point to filenames, which is redundant.
current
- [ ] thir.md
- [ ] line 7: 2022-04
- [ ] line 60: 2022-08
- [ ] traits/chalk.md
- [ ] line 4: 2022-05
proposed
- thir.md
- [ ] line 7: 2022-04
- [ ] line 60: 2022-08
- traits/chalk.md
- [ ] line 4: 2022-05
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Add sample CodeLLDB launch.json
There is a section with [instructions for setting up source analyzer in VSCode](https://rustc-dev-guide.rust-lang.org/building/suggested.html#configuring-rust-analyzer-for-rustc), but
nothing for setting up debugging with CodeLLDB. This adds a sample configuration
that may not be ideal, but appears to work for me.
To source highlight the snippet, uses JavaScript instead of JSON so that comments
do not show up as errors highlighted in red (VSCode allows comments).
* Update src/compiler-debugging.md
Co-authored-by: jyn <github@jyn.dev>
* Update src/compiler-debugging.md
Co-authored-by: jyn <github@jyn.dev>
---------
Co-authored-by: Santiago Pastorino <spastorino@gmail.com>
Co-authored-by: jyn <github@jyn.dev>
|
|
Fixes #1599
|
|
|
|
|
|
* Add Neovim configuration information
The JSON provided for VSCode works with coc and nlsp-settings.
This is verified by
https://github.com/fannheyward/coc-rust-analyzer/blob/9d8bdb9290e2a9644367594a1ceed0288506efcd/README.md
for coc, and feeding the JSON in to this schema
https://github.com/tamago324/nlsp-settings.nvim/blob/215b537cfb3fad7c9c2e352fe47a10698b0993e0/schemas/_generated/rust_analyzer.json
for validating nlsp-settings.
* Make the steps clear
First open a Rust buffer
Then update RA settings
If you don't open a buffer first then nothing will happen. This is because
the plugin makes a raw LSP RPC, so RA must be attached.
* Use separate sections for VSCode and Nvim
* Add a short section on the VSCode tasks.
|
|
Signed-off-by: Yuki Okushi <jtitor@2k36.org>
|
|
|
|
Closes https://github.com/rust-lang/rustc-dev-guide/issues/1581
|
|
|
|
It seems that this header causes "406 Not Acceptable" failures: https://github.com/rust-lang/rustc-dev-guide/actions/runs/4092776683/jobs/7057742900
|
|
Fixes https://github.com/rust-lang/rustc-dev-guide/issues/1584
|
|
Signed-off-by: ozkanonur <work@onurozkan.dev>
|
|
|
|
Signed-off-by: Yuki Okushi <jtitor@2k36.org>
|
|
Signed-off-by: Yuki Okushi <jtitor@2k36.org>
|
|
Signed-off-by: Yuki Okushi <jtitor@2k36.org>
|
|
Signed-off-by: Yuki Okushi <jtitor@2k36.org>
|
|
Signed-off-by: Yuki Okushi <jtitor@2k36.org>
|
|
Signed-off-by: Yuki Okushi <jtitor@2k36.org>
|
|
|
|
|
|
|
|
As per https://github.com/rust-lang/rust/pull/107297#discussion_r1092764740, the change broke the rust-analyzer config. Hence, changing the docs to match the new path
|
|
|
|
Right now "Clarification of build command's stdout" topic
shows up under the "Environment Variables" which is not correct.
This commit aims to fix this problem.
Signed-off-by: ozkanonur <work@onurozkan.dev>
|
|
Signed-off-by: ozkanonur <work@onurozkan.dev>
|
|
Fixes https://github.com/rust-lang/rustc-dev-guide/issues/1543
|
|
Co-authored-by: Tshepang Mbambo <tshepang@gmail.com>
|
|
|
|
Signed-off-by: Yuki Okushi <jtitor@2k36.org>
|
|
|
|
|
|
|