Felix S Klock II
00db68b612
Link from "implementing to new features" to mcp.md ( #1465 )
2022-09-16 07:06:59 +09:00
Devin Jeanpierre
01c550ef63
Add symbol-addition to the how-to for new features ( #1457 )
...
Co-authored-by: Yuki Okushi <jtitor@2k36.org>
2022-09-12 06:19:13 +09:00
Tshepang Mbambo
061577567f
use relative links
...
Used the following command, followed by some manual tweaking:
sd 'https://rustc-dev-guide.rust-lang.org/(.+).html ' '$1.md' (fd)
2022-07-17 02:32:44 +02:00
Noah Lev
ce956908d0
Clean up section about FCPs ( #1287 )
...
* I've never heard the term "pFCP" used before, so spell it out as
"proposed final comment period"
* Fix some unclear things (like implying that you need `r+` rights to
start an FCP)
* Improve the chapter's title, and make it consistent with its TOC entry
* Make some other assorted minor cleanups and improvements
2022-01-18 11:09:16 -03:00
Joshua Nelson
d8d5bbcfe3
Link to `feature_err` in stability section ( #1022 )
2021-01-19 11:47:45 -08:00
Camelid
ff24e31a36
Move instructions for adding a feature gate to "Feature Gates"
2020-11-26 20:43:36 -05:00
Joshua Nitschke
3f33422aab
correct minor grammar mistake ( #944 )
...
correct `a lots to `a lot` on implementing_new_features.md
2020-11-08 19:15:22 +01:00
mark
89f0b60ccc
fix links and names after compiler mv to compiler/
2020-08-31 05:12:13 +02:00
Ivan Veselov
87554a233a
Earlier clarification of pFCP abbreviation ( #791 )
2020-07-12 10:29:17 +09:00
Santiago Pastorino
e3c9c55b2f
Remove typo
2020-03-17 12:16:02 -05:00
Santiago Pastorino
c05ed676d2
Rename rustc-guide to rustc-dev-guide ( #601 )
...
* Rename rustc-guide to rustc-dev-guide
* rust-lang.github.io/rustc-dev-guide -> rustc-dev-guide.rust-lang.org
2020-03-10 11:01:43 -03:00
Who? Me?!
da4be3ac20
Fix broken links ( #570 )
2020-02-03 14:26:13 +09:00
LeSeulArtichaut
14c976a108
Replaced simple comment with doc comment
2020-01-29 12:19:31 -06:00
Yuki Okushi
38d8573b00
Fix links and paths
2020-01-12 14:31:55 -06:00
Mark Mansi
63156423fd
some cleanup
2019-11-14 14:14:39 -06:00
Alexander Regueiro
a14d795d7c
Updated instructions for tracking issue ( #488 )
...
* Updated instructions for tracking issue
Removed link to Forge instructions for documentation since they no longer seem to exist.
* Improved links and wording
2019-11-01 14:36:47 -03:00
Tshepang Lekhonkhobe
c46ab305be
format examples better ( #471 )
2019-10-17 21:03:46 -03:00
Tshepang Lekhonkhobe
0a2e1b74df
fix links ( #469 )
2019-10-17 16:40:38 +09:00
Mazdak Farrokhzad
6e3343158e
Update feature gating docs to fit reality ( #455 )
2019-10-01 08:40:58 -03:00
Julian Wollersberger
848faf9728
Renamed the file and title of the diagnostics chapter.
...
When I recently searched for infos in this guide on how to create
a warning, I couldn't find any. Later I found it through #14 .
The reason was that I didn't know the term 'diagnostics' and that
it is the collective term for errors, warnings and lints.
Renaming the chapter to include the word 'error' should help.
I think also including 'warning' in the title shouldn't be
neccessary, because it's close enought.
2019-05-17 11:02:08 -05:00
Alexander Regueiro
dbffbfcc6b
Small fix to code for checking feature gate
2019-03-22 15:50:31 -05:00
Who? Me?!
ab2452dcd0
Update src/implementing_new_features.md
...
Co-Authored-By: rajcspsg <raj.cs.psg@gmail.com>
2019-02-23 18:12:58 -06:00
Who? Me?!
b150cc7b63
Update src/implementing_new_features.md
...
Co-Authored-By: rajcspsg <raj.cs.psg@gmail.com>
2019-02-23 18:12:58 -06:00
Who? Me?!
d234ee80bd
Update src/implementing_new_features.md
...
Co-Authored-By: rajcspsg <raj.cs.psg@gmail.com>
2019-02-23 18:12:58 -06:00
Rajkumar Natarajan
aac85f1520
issue_130_7 updated with review comments
2019-02-23 18:12:58 -06:00