Im working on a PR for
Foldable[Iterable] instance as per #37
It seems there aren't yet any tests in alleycats. Following cats convention it seems I should copy-create an AlleycatsSuite. One slight concern: if there was a emoticon for :major_code_duplication: I'd be use it right now..
Working on #37, I hit some blockers while running tests, eg
[error] Referring to non-existent class org.scalatest.FunSuiteRegistration [error] called from org.typelevel.discipline.scalatest.Discipline$$anonfun$checkAll$2.apply(scala.Tuple2)scala.Unit
I suspect its caused by Discipline 0.4 depending on an older version of Scalatest. I'd like to try upgrading to 0.5, but the build dependencies are completely sbt-catalyzed, and its difficult to figure whats going on when https://github.com/InTheNow/sbt-catalysts/ is off the air
Arrgh, the walls are closing in. if Alleycats depends on Discipline
0.4 it hits the above error. But if it depends on
0.5 to freshen scalatest, it picks up scalacheck 1.13.x, which isnt compat with anything still on scalacheck 1.12.x, such as .. er cats, so get a different error.
On reflection, most of typelevel ecosystem sits atop scalacheck. If it breaks compat as at the 1.12 -> 1.13 boundary, thats a faultline that alot of the ecosystem needs to jump over in lockstep
Have question about how alleycats modules are supposed to work..
sbt> +publishLocalof 1.1.6 SNAPSHOT which publishes core & laws, but not tests
"org.typelevel" %% "alleycats" % "0.1.6-SNAPSHOT"as per README. But this pulls in the root project, which refs the unpublished
testsproject as a dependency . Hence
[warn] :: org.typelevel#alleycats-tests_2.11;0.1.6-SNAPSHOT: not found
This problem ought to be happening for 1.1.5 in the wild as well. Why no complaints, is no one using alleycats yet?