Incorrect inferred method type argument in Scala 3

[kpodsiad]

Describe the bug

//> using scala "3.2.0"

//> using lib "org.typelevel::cats-core:2.8.0"

import cats.data.StateT
import cats.syntax.all._
import cats.implicits._
import cats.Id

object Cats extends App {
  type IdState[A] = StateT[Id, Int, A]

  val test: IdState[Unit] =
    StateT.modify(old => old)

  test.runS(1)

}

Expected behavior

StateT.modify has correct inferred type [Id, Int]

Operating system

macOS

Editor/Extension

VS Code

Version of Metals

0.11.8+72-6567f1a3-SNAPSHOT

Extra context or search terms

No response

[tgodzik]

Thanks for reporting, it seems in semanticdb we get:
[13:4..13:17) => *[<?>, Int]

Which means we need to fix it in the compiler.

[tanishiking]

Probably related to #3935
I'll take a look 👀

[tanishiking]

Looks like this is caused by the lack of HKTypeLambda support in SemanticDB for Scala3, maybe it's time to working on it 👍

[tanishiking]

Realized synthetics for inferred type parameters have disappeared in 3.2.0 😢
scala/scala3#15877

• scala/scala3@e835dc0
• scala/scala3@097b179
• scala/scala3@097b179

[kpodsiad]

What does that mean @tanishiking ?

[tanishiking]

inferred type decoration for StateT.modify won't be available with the latest version of Scala.
(same applies to all the type apply like List(1.2.3) -> List[Int](1.2.3)).

It's regression, I'll take a look before working on lambda type support.

[kpodsiad]

It was a big PR, no one can review 8k lines of code 😞 Thanks @tanishiking

[tgodzik]

Thanks for finding this @tanishiking ! I asked Martin about it in https://github.com/lampepfl/dotty/pull/15877/files#r969241924 It's not cool that it contained so visible regressions and yet it was just merged.

[tanishiking]

Thanks, @tgodzik! Yeah, it (ignoring the regression test) shouldn't happen, but for this case, it might be easier to fix on top of the change made by Martin compared to revert it.

[tgodzik]

Thanks, @tgodzik! Yeah, it (ignoring the regression test) shouldn't happen, but for this case, it might be easier to fix on top of the change made by Martin compared to revert it.

Sure, I get that, but I think next time they should have us sign off on such changes.

[tanishiking]

Submit a PR scala/scala3#16031 to fix the regression