diff options
| author | Philipp Hansch <dev@phansch.net> | 2018-09-20 07:10:23 +0200 |
|---|---|---|
| committer | Philipp Hansch <dev@phansch.net> | 2018-09-20 07:10:23 +0200 |
| commit | f72cfc2985d1db30d351e425ec7f45f6b0a328a5 (patch) | |
| tree | 8195974ce83445126ff575d5e6b0a69cad69b8d0 | |
| parent | 2b57cec649013e5209d10c6b83ecc963b019c3e1 (diff) | |
| download | rust-f72cfc2985d1db30d351e425ec7f45f6b0a328a5.tar.gz rust-f72cfc2985d1db30d351e425ec7f45f6b0a328a5.zip | |
Mention rustup component history
| -rw-r--r-- | CONTRIBUTING.md | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index dda6ebb50d6..1341ca30ebd 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -204,14 +204,15 @@ That's why the `else_if_without_else` example uses the `register_early_lint_pass ### Fixing build failures caused by Rust -Clippy will sometimes break because it still depends on unstable internal Rust features. Most of the times we have to adapt to the changes and only very rarely there's an actual bug in Rust. +Clippy will sometimes break because it still depends on unstable internal Rust features. Most of the times we have to adapt to the changes and only very rarely there's an actual bug in Rust. Fixing build failures caused by Rust updates, can be a good way to learn about Rust internals. In order to find out why Clippy does not work properly with a new Rust commit, you can use the [rust-toolstate commit history][toolstate_commit_history]. You will then have to look for the last commit that contains `test-pass -> build-fail` or `test-pass` -> `test-fail` for the `clippy-driver` component. [Here][toolstate_commit] is an example. The commit message contains a link to the PR. The PRs are usually small enough to discover the breaking API change and if they are bigger, they likely include some discussion that may help you to fix Clippy. -Fixing build failures caused by Rust updates, can also be a good way to learn about Rust internals. +To check if Clippy is available for a specific target platform, you can check +the [rustup component history][rustup_component_history]. If you decide to make Clippy work again with a Rust commit that breaks it, you probably want to install the latest Rust from master locally and run Clippy @@ -249,3 +250,4 @@ All code in this repository is under the [Mozilla Public License, 2.0](https://w [toolstate_commit_history]: https://github.com/rust-lang-nursery/rust-toolstate/commits/master [toolstate_commit]: https://github.com/rust-lang-nursery/rust-toolstate/commit/6ce0459f6bfa7c528ae1886492a3e0b5ef0ee547 [rtim]: https://github.com/kennytm/rustup-toolchain-install-master +[rustup_component_history]: https://mexus.github.io/rustup-components-history |