Stefano Baghino aec3390904 Replace silencer plugin with built-in warning configuration (#12543) ... Since Scala 2.13.2, Scala introduced built-in support to manage warnings in a more granular fashion, thus making the silencer plugin we are currently using no longer strictly useful. Removing compiler plugins also removes friction from migrating to Scala 3 in the future. As a cherry on top, the built-in warning configuration also allows to check whether a `@nowarn` actually does anything, allowing us to proactively remove unused warnings should the need arise. [Here][1] is s a blog post by the Scala team about it. Warnings have been either solved or preserved if useful, trying to minimize the scope (keeping it at the single expression scope if possible). In particular, all remaining usages of the Scala Collection API compatibility module have been removed. Using the silencer plugin also apparently hid a few remaining usages of compatibility libraries that were used as part of the transition from Scala 2.12 to Scala 2.13 that are no longer needed. Removing those warnings highlighted those. changelog_begin changelog_end [1]: https://www.scala-lang.org/2021/01/12/configuring-and-suppressing-warnings.html		2022-01-24 15:01:35 +00:00
..
src	Replace silencer plugin with built-in warning configuration (#12543)	2022-01-24 15:01:35 +00:00
BUILD.bazel	Replace silencer plugin with built-in warning configuration (#12543)	2022-01-24 15:01:35 +00:00