@vascorsd The way I solved it till now for cases that aren't reachable was to introduce a !!! that was a good old AssertionError.. along the lines of ???. Bit of a contrived example but something like this: https://scastie.scala-lang.org/cTlwfWYDS4Wo0LWcu0gkpQ oops new link
sbt new protip: to test drive a giter8 (g8) template locally (because you want to test changes):
```
sbt new file://./cats-seed.g8
```
that `file://` bit is important.
Took `strictEqualityPatternMatching` and `subCases` for a test ride.
`strictEqualityPatternMatching` works pretty good. also across `sum`/`enum` types and `union` types. Nice!
`subCases` interfered with exhaustivity checks. Maybe I am doing something wrong. `subCases` for `sum` types to tease them out separately would be solid.
`Integer` pattern match was deemed exhaustive when shouldn't have been. (will do some more tests here.)
. @eed3si9n@mastodon.social As sbt 2 comes close to a release is it too late to try and move towards scala-cli like dependencies notation, i.e. instead of "com.casualmiracles" %% "treelog" % "1.9.5" using com.casualmiracles::treelog:1.9.5 ? I assume that newer folks will come from scala-cli to sbt so one less hurdle, also makes copy pasting things across simpler. Just a thought. And thanks once again for making sbt awesome and the good work. Can't wait for sbt 2 :)
Saw a toot about "Scala 3" Scaladoc static site generator. QOTD: Can it compile/run scala snippets embedded in docs, like mdoc?
Seems like it can: https://docs.scala-lang.org/scala3/guides/scaladoc/snippet-compiler.html
Feature parity with mdoc? Mdoc's integration with Docusaurus seems pretty nifty. sbt-typlelevel seems to have documentation covered with mdoc and laika.
What do/would you use and why?