about summary refs log tree commit diff
diff options
context:
space:
mode:
authorGuillaume Gomez <guillaume1.gomez@gmail.com>2020-01-17 19:54:07 +0100
committerGuillaume Gomez <guillaume1.gomez@gmail.com>2020-01-17 19:54:07 +0100
commite8a4b9319cbf5b3f56b3cdd8ad11e86ff7168345 (patch)
treeea37ff6d6232ada15b6ec4043ede13c883f2c204
parentbf84eb538fd16743240434b3e837b36c35719fee (diff)
downloadrust-e8a4b9319cbf5b3f56b3cdd8ad11e86ff7168345.tar.gz
rust-e8a4b9319cbf5b3f56b3cdd8ad11e86ff7168345.zip
Clean up E0199 explanation
-rw-r--r--src/librustc_error_codes/error_codes/E0199.md21
1 files changed, 15 insertions, 6 deletions
diff --git a/src/librustc_error_codes/error_codes/E0199.md b/src/librustc_error_codes/error_codes/E0199.md
index d0c12dc6f17..88130e8e5e5 100644
--- a/src/librustc_error_codes/error_codes/E0199.md
+++ b/src/librustc_error_codes/error_codes/E0199.md
@@ -1,14 +1,23 @@
+A trait implementation was marked as unsafe while the trait is safe.
+
+Erroneous code example:
+
+```compile_fail,E0199
+struct Foo;
+
+trait Bar { }
+
+unsafe impl Bar for Foo { } // error!
+```
+
 Safe traits should not have unsafe implementations, therefore marking an
 implementation for a safe trait unsafe will cause a compiler error. Removing
-the unsafe marker on the trait noted in the error will resolve this problem.
+the unsafe marker on the trait noted in the error will resolve this problem:
 
-```compile_fail,E0199
+```
 struct Foo;
 
 trait Bar { }
 
-// this won't compile because Bar is safe
-unsafe impl Bar for Foo { }
-// this will compile
-impl Bar for Foo { }
+impl Bar for Foo { } // ok!
 ```