Importing private extension function is suggested even after importing

[andrzejressel]

Compiler version

3.3.4
3.6.3

Minimized code

https://scastie.scala-lang.org/9ViV1YHoQVaaRBfcq066Kg

import Playground.Extensions.testExt

object Extensions {
  extension (s: String) {
    private def testExt() = {
    
    }
  }
}

"abc".testExt()

Output

value testExt is not a member of String, but could be made available as an extension method.

The following import might fix the problem:

  import Playground.Extensions.testExt

Expectation

Something about testExt having too restricted visibility. At least not suggesting import when it already exists.

[som-snytt]

I posted a quick draft PR that only shows candidates with restricted access if there are no others.

When showing those candidate imports, mention if there is already such an import but the member is inaccessible.

Probably the usual case is that there is one such extension, but we overlook that a member is private; sometimes we are working on a module with access, then write some code elsewhere and suddenly none of our idioms work.

I am mostly guessing about the use case.

[andrzejressel]

My case was refactoring. Private extension functions work fine from within surrounding class. During refactoring I've extracted it to separate file.