Imported From: https://issues.scala-lang.org/browse/SI-8476?orig=1
Reporter: @sschaef
Affected Versions: 2.11.0
See #8525

Jed Wesley-Smith (jedws) said:
what is this "feature" and how do we turn it off? We have a warning intolerant build and use this kind of thing for instance using the Typesafe Config library.

Is there a macro that performs no interpolation and avoids this warning?

Jed Wesley-Smith (jedws) said:
I understand what it does, but I contend it is an anti-feature.

I wrote code (in fact, I didn't I wrote a String literal) and the compiler helpfully warns me that it looks like I might have meant it to be code after all, except I didn't, if I had I would have put a macro in front of it. This is like warning if I use the Int constant 43 that perhaps 42 is a nicer number!

It makes -Xlint far less useful for us currently (we can only turn it on if we workaround the original problem, for instance by externalising the Strings in question, which is sub-optimal.

@retronym said (edited on Apr 23, 2014 5:30:04 AM UTC):
High on our todo list is to add a config option to let you filter out warnings. Hopefully in 2.11.1.

There is a tension between adding a -Yoption for each warning (maximum flexibility) vs lumping many warnings under Xlint (easier discoverability, smaller command line API).

In the meantime, you can do this yourself in SBT. I remember I helped @puffnfresh configure this a month or so ago. I'll try to dig up the example.

@retronym said:
It is in the comments of: #8410

Jed Wesley-Smith (jedws) said:
Thanks @retronym, appreciate the feedback. The suggested approach is a bit heavyweight for this though.

And, my objection to this specific warning as a valid thing stands.

@retronym said (edited on Apr 23, 2014 5:43:53 AM UTC):
It has revealed quite a few bugs, so it has value. But I agree that it needs to be configurable. I guess you can break up your strings in the mean time if you don't have too many. Or maybe

"""  @{foo} """.replaceAllLiterally("@", "$").

Closing because the example doesn't warn, for some time now, unless the ident is in scope. Also, a filtering reporter is on the horizon for the worst case scenario. Also, the warning can be disabled.