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
There are ~2900 -Wconversion warnings during compilation (out of ~3000 warnings in total). All or most of them are unprobable to cause any problems in our runtime.
But there are concerns:
Really interesting warnings could be lost in this noise.
Some of these conversion warnings are straightforward to fix. While the scale of 2900 warnings is huge, it might be good to split the work into a smaller chunks: make changes to the simplest cases, on a file or several-files basis, no more than 5-10 changes per PR etc...
Alternatives you considered
Suppress -Wconversion warning during compilation to remove noise - but for me it's better to fix it
Agreed here, most of these are due to small comparison, but there doesn't seem to be good tool for helping with applying fixes for these. Personally I think we might want to start by fixing the -Wconversion warnings in a package of mwc and work our way to bmq, mqb, and bmqbrkr from there.
Is there an existing proposal for this?
Is your feature request related to a problem?
There are ~2900
-Wconversion
warnings during compilation (out of ~3000 warnings in total). All or most of them are unprobable to cause any problems in our runtime.But there are concerns:
Info to read:
https://gcc.gnu.org/wiki/NewWconversion
Describe the solution you'd like
Some of these conversion warnings are straightforward to fix. While the scale of 2900 warnings is huge, it might be good to split the work into a smaller chunks: make changes to the simplest cases, on a file or several-files basis, no more than 5-10 changes per PR etc...
Alternatives you considered
Suppress
-Wconversion
warning during compilation to remove noise - but for me it's better to fix itContribution workflow
main
branch buildBuild BlazingMQ
-Wconversion
to find an intersting place to fixThe text was updated successfully, but these errors were encountered: