Michał Pałka

Thanks for reporting. Actually an attempt to bump spark to 4.0.0-preview2 caused a few more issues for me: * I had to add `//> using jvm 17` to `project.scala` because...

I did reproduce the issue directly in this repo, which is built using scala-cli. I guess you meant `spark 4`, not `scala 4` 😆 Currently I'm struggling to find time...

This might not be obvious at a first glance, but IMO this is not a bug against the language specification. The linked documentation page describes parameter tupling for **functions**, which...

Or maybe just my understanding of desugaring of context lambdas is quite limited, because TBH I'm quite surprised that ```scala foo { (ordA, ordB) ?=> (0 to 5).map(A(_)).sorted(using ordA) }...

If I understand your use case correctly: * You want to abstract over the context parameters of a context function (arity and types of parameters) * You already have a...

Trying to bisect that. The regression seems to have happened somewhere between `3.3.1-RC1-bin-20230215-006e2e4-NIGHTLY` and `3.3.1-RC1-bin-20230216-2507577-NIGHTLY`

Bisected further with `scala-cli project/scripts/bisect.scala -- --bootstrapped --releases 3.3.1-RC1-bin-20230215-006e2e4-NIGHTLY...3.3.1-RC1-bin-20230216-2507577-NIGHTLY compile /tmp/bisect/GraphTraversal.scala`. This points to https://github.com/scala/scala3/commit/c830ad26733a633a6d58b93e9bd66ff7b67b65ed

The problem also occurs if `Testme.Hello` isn't referenced in scala code but instead in java code one references first `Testme$.Hello` and then `Testme.Hello`

I started to wander if this SIP could help resolve this issue: https://github.com/scala/scala3/issues/18009 In short, the problem there is that an invocation of a curried method added by a refinement...

OK, right - most of the compiler core code resides in `dotty.tools.dotc` package. However I had an impression that it's just because it would be too much work to migrate...