what build tooling do we want for scalaz8?

[fommil]

There are a lot of really great build tools available nowadays, such as scalafmt, scalafix and a new linter.

I personally prefer to have as much automated as possible, included format on compile, what's the general feeling?

[jdegoes]

Automate as much as possible. 👍

[jvz]

If possible, scalafix templates to migrate from scalaz7 to scalaz8 would be super useful.

[ChristopherDavenport]

You may already be aware but as a tale from the trench, when http4s implemented scalafmt on compile we got hit with an initial round of memory errors, and secondly it was much slower to compile.

It was eventually frustrating enough to be moved to a different command so that changes could be made normally and then formatted and automated testing happened in our new sbt ci command.

If you were already aware of these concerns, my apologies for repeating them.

[fommil]

scalafmt definitely has those problems... sadly. I still think it's worth it. The way it is launched for every project and every configuration is exceptionally inefficient.

[jdegoes]

Migration would be very nice. Disappointed to hear about the effect on compilation.

[fommil]

An option would be to use the scalafmt CLI in CI and not make it part of the sbt build, which doesn't interfere (but can be a bit irritating sometimes)

[tonymorris]

I doubt my opinion is popular, but it is:

1. Scalaz used to be built with a .hs script, many years ago.
2. Nothing better has ever been demonstrated to me.

[puffnfresh]

I was going to say the same thing as @tonymorris. The build should be Shake, or similar.

[fommil]

I have made my peace with sbt. Although it has many flaws.

[jvz]

Scalaz used to be built with a .hs script, many years ago.

Wait, you can build Scala programs with Haskell scripts? Now this I'd like to see.