twitter/storehaus — pull request #108 by softprops (2013-05-09 00:01:10+00:00)
Title: Core bijections

This is semi-notable change. What changed changed in this branch was

1) storehaus-core now depends on bijection-core. This allows ConvertedStore to live in a [less awkward home](https://github.com/twitter/storehaus/issues/104).

2) storehaus-algebra, only depends on bijection-core transitively through its dependency on storehaus-core

3) There now exists a com.twitter.storehaus.ConvertedStore. com.twitter.storehaus.algebra.ConvertedStore was marked deprecated

4) AlgebraicStore was a half home for methods that really belonged on EnrichedStore, methods that operated on Stores instead of MergableStores. These methods were ported over to Store and Enriched store. The methods in AlgebraicStore were marked deprecated.

Things to note.
* I don't know what the next version of storehaus will be, but what ever it is, the release that this goes into should be in sync with the version annotated in @deprecated.
* I don't think there are any breaking changes here, just deprecations, but I'd like a second pair of eyes to confirm that everything that should have been brought over makes sense and I didn't miss anything. It would be nice to get it done all at once on this branch. The way I understand stores in general and the pattern going on here is as follows. There are instances of types of stores and a companion object for each of those instance types that holds methods which take an instance of a store and some extra arguments and returns a new wrapping for a given type of store, `enriching` it essentially. Currently there are ReadableStores, Stores ( readable with writable methods ) which live under core, then there are mergables which live under algebra. Let me know if thats the right way to look at the lay of the land and if everything now has a home that fits that model.