Sergey Torgashov
Sergey Torgashov
@armanbilge just to clarify: you mean sbt-typelevel `0.5.x` line (which is not released yet), but not the `0.4.x` one, don't you? Because in 0.4 all unused warnings are still disabled...
> But ok, we still need to think about this for 0.5.x then. Oh yeah, I do think about it. But the thing is that if we'd like to switch...
@som-snytt it would be great if you could take a look at typelevel/scalac-options#9 and share your thoughts/suggestions in there. thanks!
@armanbilge is [this](https://github.com/typelevel/mouse/pull/370#issuecomment-1259005714) thread related to your initial concern?
Hmm.. If I'm not mistaken, it became a compiler option in Scala 3, didn't it?
Right.. I'm just thinking about integration with `scalac-options` and how to address such differences..
@droidmonkey , just wondering – was it completed as "fixed" or "won't be fixed"? I'm asking because now I have **v2.7.1** and experience exactly the same issue as here in...
Just to clarify: the main purpose of this PR is to make `HttpVersion` pretending it is a case class but without `copy` – is that it or am I missing...
There are at least 2 strategies available for suppressing/removing `.copy` methods from case classes without re-implementing all their other fuctionality: 1. Simpy add `private def copy() = ()` to the...
> Note that this still generates an unapply method. Correct. And (I think) it is absolutely safe in contrast to the `apply` one. Because it is just an extractor after...