Skip to content

unchecked warnings in REPL of recent 2.13.x build #11902

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Jasper-M opened this issue Mar 5, 2020 · 3 comments
Closed

unchecked warnings in REPL of recent 2.13.x build #11902

Jasper-M opened this issue Mar 5, 2020 · 3 comments
Assignees
Milestone

Comments

@Jasper-M
Copy link

Jasper-M commented Mar 5, 2020

Welcome to Scala 2.13.2-bin-f86e6b (Java HotSpot(TM) 64-Bit Server VM, Java 1.8._152).
Type in expressions for evaluation. Or try :help.

scala> :pa
// Entering paste mode (ctrl-D to finish)

sealed abstract class Value
object Value {
    final case class Num(value: Double) extends Value
    final case class Str(value: String) extends Value
    final case class Bool(value: Boolean) extends Value
}

// Exiting paste mode, now interpreting.

warning: 3 unchecked warnings; for details, enable `:setting -unchecked' or `:replay -unchecked'
class Value
object Value

scala> :warn
           final case class Num(value: Double) extends Value
                            ^
On line 3: warning: The outer reference in this type test cannot be checked at run time.
           final case class Str(value: String) extends Value
                            ^
On line 4: warning: The outer reference in this type test cannot be checked at run time.
           final case class Bool(value: Boolean) extends Value
                            ^
On line 5: warning: The outer reference in this type test cannot be checked at run time.

Those warnings weren't there in 2.13.1.

@SethTisue SethTisue added this to the 2.13.2 milestone Mar 5, 2020
@SethTisue SethTisue added the repl label Mar 5, 2020
@dwijnand
Copy link
Member

dwijnand commented Mar 5, 2020

Same as #11534? (via @som-snytt)

@Jasper-M
Copy link
Author

Jasper-M commented Jun 10, 2020

Looks like the fix didn't get merged forward in time for 2.13.2.

@SethTisue
Copy link
Member

hmm, that's odd. but in any case, HEAD of 2.13.x has the change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants