Tap needs to take A => Any instead of A => Unit
Added error-appending Validation combinator for "search for success"
mechanics; an alternative to orElse-type behavior that appends errors.
Added tests for Validation#findSuccess
Add Foldable1 and Traverse1

This provides a better abstraction for when things are "non-empty" and
removes partial functions from Foldable and Traverse.

* Loosens Foldable1 to Semigroup (from Monoid)
* Loosens Traverse1 to Apply (from Applicative)
* Id has a Traverse1
* Product has a Traverse1
* NonEmptyList has a Traverse1
* Tree has a Traverse1

    Traversable <---- Foldable
         |               |
         v               v
    Traversable1 <--- Foldable1

See http://hackage.haskell.org/package/semigroupoids
Add test of foldl1 and foldr1 for NonEmptyList
Add maximum and minimum back to Foldable

Rename Foldable1's to maximum1 and minimum1.
Merge pull request #241 from pufuwozu/scalaz-seven

Add Foldable1 and Traverse1
Be explicit about which implicit we're passing.

Implicit search actually works too well in Scala 2.11.0-SNAPSHOT,
and it not reports an ambiguity:

    [error] /Users/jason/code/scalaz/core/src/main/scala/scalaz/Distributive.scala:29: ambiguous implicit values:
    [error]  both value idInstance in package scalaz of type => scalaz.Traverse1[scalaz.Id.Id] with scalaz.Each[scalaz.Id.Id] with scalaz.Monad[scalaz.Id.Id] with scalaz.Comonad[scalaz.Id.Id] with scalaz.Cojoin[scalaz.Id.Id] with scalaz.Distributive[scalaz.Id.Id] with scalaz.Zip[scalaz.Id.Id] with scalaz.Unzip[scalaz.Id.Id] with scalaz.Cozip[scalaz.Id.Id]
    [error]  and value evidence$4 of type scalaz.Functor[G]
    [error]  match expected type scalaz.Functor[G]
    [error]     distribution.run(fa)(f)
    [error]     ^

It might in fact be prudent to remove the implicit idInstance from
the package object scalaz. I know we've been flip-flopping on this
matter, the advantage of a protracted development cycle is that we're
testing with no less than three major versions of the Scala compiler,
so we're able to find out when we've been relying on unspecified
behaviour!
A simpler fix for the 2.11.0-SNAPSHOT ambiguity.

 - explicitly provide the type argument for distribute.
add leftMap/rightMap to BifunctorOps

Signed-off-by: Mike (stew) O'Connor <stew@vireo.org>
Order for NonEmptyList.
Merge pull request #245 from S11001001/topic/nel-order

Order for NonEmptyList
fix error message in Heap
add a safe tap operator, make clear that the other one is unsafe
Merge pull request #237 into scalaz-seven