Oleg Pyzhcov

@alexandru Scala doesn't fallback to `filter` anymore: - [Language spec on for-comprehension](https://www.scala-lang.org/files/archive/spec/2.13/06-expressions.html#for-comprehensions-and-for-loops) - [PR removing the rewrite](https://github.com/scala/scala/pull/5252) I guess you could try to do what the PR did in reverse,...

Yeah I'd have to look for a new workaround for that warning. The linter has always produced bogus warnings in that scenario, but I was able to silence it using...

> The i$implicit$1 gets passed explicitly, and it seems that in 2.13.5 the validation rules were changed to warn about such implicitly explicit usage. Oh by the way, bm4 doesn't...

I can't reproduce that. Which version of bm4, Scala and combination of flags are you using?

Seems `-Ywarn-unused:params` is just busted irrespective of plugin. E.g. it warns in this simple case: ```scala object test extends App { val x = for { n 0 } yield...

That tree looks like one between parser and bm4 first phase, so it won't tell you anything. What you want to check is tree right after `typer` or `bm4-typer` It's...

Sorry, it appears to be fixed in 0.3.1, please try updating

That's odd. I'll leave it open to look into later.

I just received the same error compiling this exact file: https://github.com/oleg-py/arcomage-challenge/blob/d47b70cfb5521ad22bab88488c830d69569c0da6/core/src/main/scala/ac/game/GameConditions.scala It only uses `Greater` refinement and automatic conversions. Restarting sbt made the problem go away.

The common thing to do with unused implicits is just ```scala object Foo { implicit def decodeFoo[A](implicit decode0: Decoder[A]): Decoder[Foo[A]] = { val _ = decode0 deriveDecoder[Foo[A]] } } ```...