Skip to content
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

Multiple syntax warnings in REPL #10130

Closed
scabug opened this issue Jan 1, 2017 · 2 comments · Fixed by scala/scala#7467
Closed

Multiple syntax warnings in REPL #10130

scabug opened this issue Jan 1, 2017 · 2 comments · Fixed by scala/scala#7467

Comments

@scabug
Copy link

scabug commented Jan 1, 2017

This is a little funky:

$ scala
Welcome to Scala 2.12.1 (Java HotSpot(TM) 64-Bit Server VM, Java 1.8.0_111).
Type in expressions for evaluation. Or try :help.

scala> '\060'
<console>:1: warning: Octal escape literals are deprecated, use \u0030 instead.
'\060'
 ^
<console>:2: warning: Octal escape literals are deprecated, use \u0030 instead.
'\060'
 ^
<console>:12: warning: Octal escape literals are deprecated, use \u0030 instead.
       '\060'
        ^
res0: Char = 0

scala> 
@scabug
Copy link
Author

scabug commented Jan 1, 2017

Imported From: https://issues.scala-lang.org/browse/SI-10130?orig=1
Reporter: @som-snytt
Affected Versions: 2.12.1

@scabug
Copy link
Author

scabug commented Jan 17, 2017

@som-snytt said:
Low hanging fruit tastes best.

scala/scala#5647

@scabug scabug closed this as completed Feb 8, 2017
@scabug scabug added this to the 2.12.2 milestone Apr 7, 2017
eed3si9n added a commit to eed3si9n/scala that referenced this issue Nov 27, 2018
In scala#6325 Seth reported that procedure syntax
deprecation warnings are not displayed on REPL.
This is because warnings were filtered out by `withoutWarnings` in scala#5647 to fix scala/bug#10130.
On 2.13.x, it seems to work ok without the `withoutWarnings` filter during parse.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants