split ServiceExt trait

actix · Dec 13, 2018 · bf9bd97 · bf9bd97
1 parent 61939c7
commit bf9bd97
Show file tree

Hide file tree

Showing 3 changed files with 14 additions and 1 deletion.
diff --git a/actix-service/CHANGES.md b/actix-service/CHANGES.md
@@ -1,5 +1,12 @@
 # Changes
 
+## [0.1.3] - 2018-12-12
+
+## Changed
+
+* Split service combinators to separate trait
+
+
 ## [0.1.2] - 2018-12-12
 
 ### Fixed

diff --git a/actix-service/Cargo.toml b/actix-service/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "actix-service"
-version = "0.1.2"
+version = "0.1.3"
 authors = ["Nikolay Kim <[email protected]>"]
 description = "Actix Service"
 keywords = ["network", "framework", "async", "futures"]

diff --git a/actix-service/src/lib.rs b/actix-service/src/lib.rs
@@ -50,7 +50,11 @@ pub trait Service<Request> {
     /// Calling `call` without calling `poll_ready` is permitted. The
     /// implementation must be resilient to this fact.
     fn call(&mut self, req: Request) -> Self::Future;
+}
 
+/// An extension trait for `Service`s that provides a variety of convenient
+/// adapters
+pub trait ServiceExt<Request>: Service<Request> {
     /// Apply function to specified service and use it as a next service in
     /// chain.
     fn apply<T, I, F, Out, Req>(
@@ -146,6 +150,8 @@ pub trait Service<Request> {
     }
 }
 
+impl<T: ?Sized, Request> ServiceExt<Request> for T where T: Service<Request> {}
+
 /// Creates new `Service` values.
 ///
 /// Acts as a service factory. This is useful for cases where new `Service`