-
Notifications
You must be signed in to change notification settings - Fork 44
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
Compile warnings #69
Comments
What kind of warnings? There could be signed-unsigned conversion/comparison warnings over the place. g++/clang builds on macos/linux are (mostly) warning-free with One place is the usage of tmpfile in tests, but it is safe and actually should be that way. |
One of these warnings are signed-unsigned conversion yes. It seems to be on by default for Windows. We can I guess tune warnings for windows too. |
Ah, unsafe Windows CRT functions. I see. |
On warnings: (I will update this list) Ignore:
|
While porting I noticed quite high amount of compile warnings.
What is your stance on it?
Should it be eventually fixed?
The text was updated successfully, but these errors were encountered: