v0.9.2: partial revert of previous "fix" and actual fix for transformer bug

What's Changed

• Transformer: Construct the right recursive types by @dfinkel in #69

Full Changelog: v0.9.1...v0.9.2

v0.9.1 -- Fix bug in ReverseTranform

What's Changed

• transform: unmangle: Create appropriate nil values in maybeRecursivelyUnmangle by @dfinkel in #68

Full Changelog: v0.9.0...v0.9.1

v0.9.0 Type-safe dials (1.0 RC)

First release!
Relative to master two weeks ago:

• Dials clients no longer need to type-assert the returned value, as the Dials type's methods and callbacks now use concrete types parameterized on the configuration-type.
• Subpackage organization
  • Dials Source implementations now live under the sources subpackage
  • Dials Decoder implementations now live under the decoders subpackage
• The Blank source now returns an error not only reflecting the specific source it's substituting in, but also the stacked configuration from Dials. As such, it's no longer necessary to setup a newconfig or error callback (or watch the Events() channel) to safely use that type (which greatly simplified the code in the ez package).
• Runtime callback registration is now possible with the RegisterCallback method (it returns an unregistration callback).

Note: some of these changes are API-breaking, as introducing generics should improve the user-experience significantly, and we took the opportunity to do a little bit of cleanup.
(we also have not spent the time to update the README or many of the docs yet, that will precede any full announcement)