update doc and history and prepare for release

HISTORY.rst

@@ -2,6 +2,10 @@
 History
 =======
 
+0.10.0 (2020-7-1)
+-----------------
+
+* Support for return values in signatures
 
 0.9.2 (2019-10-1)
 -----------------

README.rst

@@ -119,7 +119,8 @@ Features
 --------
 
 * Define reusable parameters with defaults, conversion and validation logic, documentation, preferred position in the signature and whether keyword-only.
-* Define reusable signatures as ordered maps from names to parameters.
+* Define reusable return values with conversion and validation logic and documentation.
+* Define reusable signatures as ordered maps from names to parameters with optional return value definition.
 * Combine signatures to create complex ones on top of simple ones.
 * Decorate functions and methods with their signatures. Enforced at load time. Conversion and validation logic executed at call time.
 * Not hot about signatures? You can just use parameters as in::

docs/usage.rst

@@ -8,7 +8,7 @@ To use autosig in a project::
 
 To define a signature::
 
-    api_sig = Signture(x = param(default=0, converter=int))
+    api_sig = Signature(x = param(default=0, converter=int))
 
 To associate that signature with a function::
 
@@ -29,6 +29,10 @@ Simple signatures can be combined to for more complex ones::
 
     sig = Signature(x=param())+Signature(y=param())
 
+Signatures can now include return values::
+
+    api_sig = Signature(Retval(validator=int), x = param(default=0, converter=int))
+
 You can skip signatures altogehter and just capture commonalities between arguments with the argumentless form of the decorator::
 
     x_arg = param(...)