feat/container: put sequential layer into container dir

BREAKING CHANGE: the Sequential and SequentialConfig struct is no longer
available via leaf::layers::common::

Author: MichaelHirn

src/layers/common/mod.rs

@@ -16,7 +16,6 @@ pub use self::linear::{Linear, LinearConfig};
 pub use self::log_softmax::LogSoftmax;
 #[cfg(all(feature="cuda", not(feature="native")))]
 pub use self::pooling::{Pooling, PoolingConfig, PoolingMode};
-pub use self::sequential::{Sequential, SequentialConfig};
 pub use self::softmax::Softmax;
 
 #[cfg(all(feature="cuda", not(feature="native")))]
@@ -25,7 +24,6 @@ pub mod linear;
 pub mod log_softmax;
 #[cfg(all(feature="cuda", not(feature="native")))]
 pub mod pooling;
-pub mod sequential;
 pub mod softmax;
 
 /// Provides common utilities for Layers that utilize a filter with stride and padding.

src/layers/container/mod.rs

@@ -0,0 +1,15 @@
+//! Provides container layers.
+//!
+//! For now layers in container should be discribed as layers that are used
+//! to connect multiple layers together to create 'networks'.
+#[macro_export]
+macro_rules! impl_ilayer_common {
+    () => (
+        fn exact_num_output_blobs(&self) -> Option<usize> { Some(1) }
+        fn exact_num_input_blobs(&self) -> Option<usize> { Some(1) }
+    )
+}
+
+pub use self::sequential::{Sequential, SequentialConfig};
+
+pub mod sequential;

src/layers/common/sequential.rs src/layers/container/sequential.rs

@@ -2,8 +2,7 @@
 //!
 //! These layers provide different type of operations to the data Blobs
 //! that flow through them.
-//! The operations provided by the layers can be
-//! roughly grouped into four categories:
+//! The operations provided by the layers are grouped into five categories:
 //!
 //! * [__Activation__][mod_activation]</br>
 //! Activation Layers provide element-wise operations and produce one top Blob
@@ -31,6 +30,12 @@
 //! Utility Layers follow the general behavior of a layer, like the other types
 //! do.
 //!
+//! * [__Container__][mod_container]</br>
+//! Container layers take `LayerConfig`s and connect them on initialization, which
+//! creates a "network". But as container layers are layers one can stack multiple
+//! container layers on top of another and compose even bigger container layers.
+//! Container layers differ in how they connect the layers that it receives.
+//!
 //! For more information about how these layers work together, see the
 //! documentation for the general [Layer module][3].
 //!
@@ -41,6 +46,7 @@
 //! [mod_common]: ./common/index.html
 //! [mod_loss]: ./loss/index.html
 //! [mod_utility]: ./utility/index.html
+//! [mod_container]: ./container/index.html
 
 /// Implement [ILayer][1] for [activation layers][2].
 /// [1]: ./layer/trait.ILayer.html
@@ -60,7 +66,6 @@ pub use self::common::{
 pub use self::common::{
     Linear, LinearConfig,
     LogSoftmax,
-    Sequential, SequentialConfig,
     Softmax,
 };
 
@@ -73,7 +78,12 @@ pub use self::utility::{
     Reshape, ReshapeConfig,
 };
 
+pub use self::container::{
+    Sequential, SequentialConfig,
+};
+
 pub mod activation;
 pub mod common;
 pub mod loss;
 pub mod utility;
+pub mod container;