Reduce compilation warnings in tests
#4083
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an attempt to improve code hygiene a bit by reducing amount of warnings while compiling the
testsJVM
,testsJS
andtestsNative
modules.No tests are removed nor disabled, no other changes besides the
tests*
modules. But some tests were tossed over different suites or suite mixins.Caveat: because
@nowarn
annotation is not supported in Scala 3.0.x, for this cross-build configuration most of the warnings will still remain. But things should get improved once the project upgrades to Scala 3.1.x.Note: also in all changed files the "Organize Imports" (vs-code+metals) command was applied.