-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reduce compilation warnings in tests
#4083
Conversation
b09ec19
to
98478c8
Compare
This PR is still awaiting its hero who would dare to review it :) |
98478c8
to
7e21c4a
Compare
7e21c4a
to
045ac91
Compare
Hi folks! May I draw a fraction of your attention to this PR please? There's nothing dangerous with it – it just reduces compilation warnings from tests which can help to alleviate developer experience tremendously while they're working on any tests as well as coding in any IDE. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@rossabaker @johnynek thank you guys! |
Thank you! Sorry for the latency! |
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.