Allow dead_code in tests and examples

derive_builder/examples/channel.rs

@@ -1,3 +1,5 @@
+#![allow(dead_code)]
+
 #[macro_use]
 extern crate derive_builder;
 

derive_builder/examples/custom_error.rs

@@ -3,6 +3,7 @@
 //! This relies on how the generated build function is constructed; the validator
 //! is invoked in conjunction with the `?` operator, so anything that converts to
 //! the generated `FooBuilderError` type is valid.
+#![allow(dead_code)]
 
 #[macro_use]
 extern crate derive_builder;

derive_builder/examples/custom_error_generic.rs

@@ -1,6 +1,7 @@
 //! This example shows combining generics with custom errors and validation.
 //!
 //! Note the use of the type parameter in the `#[builder(...)]` attribute.
+#![allow(dead_code)]
 
 #[macro_use]
 extern crate derive_builder;

derive_builder/examples/readme_example.rs

@@ -1,6 +1,7 @@
 // NOTE: generate fully expanded version with `cargo expand`.
 //
 //       cargo expand --example readme_example
+#![allow(dead_code)]
 
 #[macro_use]
 extern crate derive_builder;

derive_builder/tests/derive_trait.rs

@@ -1,3 +1,5 @@
+#![allow(dead_code)]
+
 #[macro_use]
 extern crate derive_builder;