-
Notifications
You must be signed in to change notification settings - Fork 141
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
Handle cargo build
warnings
#1337
Handle cargo build
warnings
#1337
Conversation
Bencher Report
Click to view all benchmark results
|
Bencher Report
Click to view all benchmark results
|
Bencher Report
Click to view all benchmark results
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1337 +/- ##
==========================================
+ Coverage 19.11% 19.14% +0.02%
==========================================
Files 166 164 -2
Lines 11047 11030 -17
==========================================
Hits 2112 2112
+ Misses 8935 8918 -17
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
The ones generated in |
hmm.. it might take a while until we get there. Any reason why not to remove dead code before that? |
I would say just to remember to properly fix the corresponding warnings during refactoring PRs.. but I'm not totally against disabling dead_code as you are doing here. |
724a31d
to
b667499
Compare
b667499
to
4e881e9
Compare
going with |
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.
tACK
resolves #1096 and #1048
None of the dead code is removed and only marked with
dead_code
macro.