suppressing the warning but not the error
See original GitHub issuewe are able to suppress this warning
[error] src/main/scala/scalaz/ioeffect/Void.scala:33:26: dead code following this construct
[error] private[ioeffect] object VoidImpl extends VoidModule with VoidSyntax {
[error] ^
but when scalacOptions in Compile += "-Xfatal-warnings"
is added, we get
[info] Compiling 13 Scala sources to /tmp/fommil-sbt/home/fommil/Projects/scalaz-ioeffect/target/scala-2.12/classes ...
[error] No warnings can be incurred under -Xfatal-warnings.
[error] one error found
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
How to suppress all GCC warning but errors - Stack Overflow
To suppress all warnings (but not errors) use the -w flag. Share.
Read more >Warning Options (Using the GNU Compiler Collection (GCC))
Warnings are diagnostic messages that report constructions that are not inherently erroneous but that are risky or suggest there may have been an...
Read more >Suppress compiler warnings - Visual Studio - Microsoft Learn
In Solution Explorer, choose the project or source file in which you want to suppress warnings. On the menu bar, choose View >...
Read more >4.8. Options to Request or Suppress Warnings
Warnings are diagnostic messages that report constructions which are not inherently erroneous but which are risky or suggest there may have been an...
Read more >Options to Request or Suppress Warnings — gcc 6 ... - Fedora
Warnings are diagnostic messages that report constructions that are not inherently erroneous but that are risky or suggest there may have been an...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think it would be good if all plugins tried to be good citizens to the best of their ability, with silencer at the end of the list as the nuclear option.
OK, I think I nailed it.
There is a clash between
silencer
andsemanticdb
compiler plugin. Both have their own error/warning reporter which wraps the original reporter. They should totally be able to wrap each other and work together just fine but it’s important to ensure that thesilencer
reporter wraps thesemanticdb
reporter and not the other way. This means thatsilencer
plugin must be applied aftersemanticdb
plugin, which can be forced using this workaround: