-
Notifications
You must be signed in to change notification settings - Fork 122
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
several code warnings related to deprecated funcs, truncation, and unused vars #71
Comments
Thank you for the thorough report! |
@diablodale if you are well versed on MSVC side of things, you can create a PR addressing some of those and I'll take a look at it. Otherwise will check those out once I have more time on hands. |
I can prob do some of these. I suspect many of them are related to 64-bit compile. GSL::narrow_cast<> is the modern way to do those truncations, e.g. https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#es46-avoid-lossy-narrowing-truncating-arithmetic-conversions. While the deprecated/unsafe functions like I'll look either way. Gimme a week. |
I'd like to bring in GSL as well - don't know about public usage though. I guess it would be okay if used only in private headers/sources. What do you think? I already took a quick look at the Thanks a lot! |
@themarpe , to which branch should I do work and submit PRs? |
@diablodale to |
I have a PR ready, but ctest is failing on the unchanged develop branch #77 I request your input and/or review on several topics -- they will be highlighted in the PR. I can always update the PR. 😄 I might have several commits in the PR as we work through it. I will gladly squash them all into one for the final. |
Thank you! |
@themarpe where does your team stand on the idea to use I would recommend to first use its |
I'm in favor of it - also for the GSL should be also available as is by Hunter although not sure if the latest. We'd have to specify the version for it if we use it publically, as we did with nlohmann json the other day |
Build results in 10+ warnings of code style, deprecation, truncation, etc. These can likely be resolved easily by minor code changes, or hiding the warnings with pragmas.
Setup
develop
branch 126f5fcRepro
Result
Expected
No warnings of unused vars, deprecated functions, potentially unsafe truncation, etc.
The text was updated successfully, but these errors were encountered: