Some small fixes

This commit is contained in:
Takayuki Nakata 2020-08-03 23:32:19 +09:00 committed by Who? Me?!
parent cb87579a2f
commit 574f709928
2 changed files with 2 additions and 3 deletions

View File

@ -17,7 +17,6 @@ TODO: what is the vetting process?
## Permitted dependencies ## Permitted dependencies
The `tidy` tool has [a list of crates that are allowed]. To add a The `tidy` tool has [a list of crates that are allowed]. To add a
dependency that is not already in the compiler, you will need to add it to these dependency that is not already in the compiler, you will need to add it to the list.
crates.
[a list of crates that are allowed]: https://github.com/rust-lang/rust/blob/19ecce332e56941ea0dd2a805270faa102acdb14/src/tools/tidy/src/deps.rs#L59 [a list of crates that are allowed]: https://github.com/rust-lang/rust/blob/19ecce332e56941ea0dd2a805270faa102acdb14/src/tools/tidy/src/deps.rs#L59

View File

@ -76,7 +76,7 @@ Furthermore this attribute is needed to mark an intrinsic as callable from
Macros, compiler desugarings and `const fn`s expose their bodies to the call Macros, compiler desugarings and `const fn`s expose their bodies to the call
site. To work around not being able to use unstable things in the standard site. To work around not being able to use unstable things in the standard
library's macros, there's the `#[allow_internal_unstable(feature1, feature2)]` library's macros, there's the `#[allow_internal_unstable(feature1, feature2)]`
attribute that allows the given features for usage in stable macros or attribute that allows the given features to be used in stable macros or
`const fn`s. `const fn`s.
Note that `const fn`s are even more special in this regard. You can't just Note that `const fn`s are even more special in this regard. You can't just