Format the code

[rust.git] / CONTRIBUTING.md

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 69bc3546ba05fbbf3be311dafb200b31045f872e..09f4f34b98d7231c6813cf0e3e3cbc279c8e548e 100644 (file)
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -2,6 +2,8 @@
 
 Hello fellow Rustacean! Great to see your interest in compiler internals and lints!
 
+**First**: if you're unsure or afraid of _anything_, just ask or submit the issue or pull request anyway. You won't be yelled at for giving it your best effort. The worst that can happen is that you'll be politely asked to change something. We appreciate any sort of contributions, and don't want a wall of rules to get in the way of that.
+
 Clippy welcomes contributions from everyone. There are many ways to contribute to Clippy and the following document explains how
 you can contribute and how to get started.
 If you have any questions about contributing or need help with anything, feel free to ask questions on issues or
@@ -78,12 +80,8 @@ First, create a new UI test file in the `tests/ui/` directory with the pattern y
 
 ```rust
 // ./tests/ui/my_lint.rs
-
-// The custom_attribute needs to be enabled for the author lint to work
-#![feature(plugin, custom_attribute)]
-
 fn main() {
-    #[clippy(author)]
+    #[clippy::author]
     let arr: [i32; 1] = [7]; // Replace line with the code you want to match
 }
 ```
@@ -152,13 +150,7 @@ Therefore you should use `tests/ui/update-all-references.sh` (after running
 Manually testing against an example file is useful if you have added some
 `println!`s and test suite output becomes unreadable.  To try clippy with your
 local modifications, run `cargo run --bin clippy-driver -- -L ./target/debug input.rs` from the
-working copy root. Your test file, here `input.rs`, needs to have clippy
-enabled as a plugin:
-
-```rust
-#![feature(plugin)]
-#![plugin(clippy)]
-```
+working copy root.
 
 ### How Clippy works