Misleading error message for inaccessible class

[scabug]

depends on "com.typesafe" % "config" % "1.0.2"

package com.zcompany.mirror

import com.typesafe.config.Config
import com.typesafe.config.impl.SimpleConfig

abstract class ConfigWithFallback(val config:Config) extends SimpleConfig {

}

error message is missleading:

[error] C:\mirror\src\main\scala\ConfigWithFallback.scala:6: class SimpleConfig in package impl cannot be accessed in package com.typesafe.config.impl
[error] abstract class ConfigWithFallback(val config:Config) extends SimpleConfig {
[error] ^
[error] one error found

1. package listed in can not be accessed in package is wrong it should be com.*

2. in package impl - full package name should be used there

[scabug]

Imported From: https://issues.scala-lang.org/browse/SI-7727?orig=1
Reporter: Radim Kolar (hsn)
Affected Versions: 2.10.2

[SethTisue]

easy to test with scala-cli --dep com.typesafe:config:1.0.2

Scala 2.13.16: "error: not found: type SimpleConfig"
Scala 3.6.3: "Not found: type SimpleConfig"

but anyway, the original report doesn't make much sense to me.

[som-snytt]

with cli one can still witness

➜  snips scala-cli compile --server=false -S 2.12.20 -Vprint:typer t7727.scala
/home/amarki/snips/t7727.scala:9: error: class SimpleConfig in package impl cannot be accessed in package com.typesafe.config.impl
abstract class ConfigWithFallback(val config:Config) extends SimpleConfig
                                                             ^
[[syntax trees at end of                     typer]] // t7727.scala

that is trying to tell you where it is and how you tried to access it (the prefix).

Arguably, the old message is more helpfuller. It tells you there is such a class, but it is not accessible.

OTOH, the modern message says, For you, there is no such class. How often I've heard that, at school, or waiting outside a club!

Edit: I didn't check, but I wonder if changes around typing parents accounts for the difference.