You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest release of the sbt-tpolecat plugin (https://github.com/typelevel/sbt-tpolecat/releases/tag/v0.4.2) fixes a bug that caused some compiler settings not to be used. These settings enable a large number of additional linting rules, and PoolQ has code that does not pass these lint rules.
We should enable the latest version of the plugin and fix all the compilation warnings. The vast majority of them appear to harmless "discarded non-Unit value" warnings in test assertions (which operate by side-effect). We could probably fix many of them by porting tests from ScalaTest to munit, but they can also be handled on a one-off basis by prefixing the problematic assertions with val _ = .
The text was updated successfully, but these errors were encountered:
The latest release of the sbt-tpolecat plugin (https://github.com/typelevel/sbt-tpolecat/releases/tag/v0.4.2) fixes a bug that caused some compiler settings not to be used. These settings enable a large number of additional linting rules, and PoolQ has code that does not pass these lint rules.
We should enable the latest version of the plugin and fix all the compilation warnings. The vast majority of them appear to harmless "discarded non-Unit value" warnings in test assertions (which operate by side-effect). We could probably fix many of them by porting tests from ScalaTest to munit, but they can also be handled on a one-off basis by prefixing the problematic assertions with
val _ =
.The text was updated successfully, but these errors were encountered: