Skip to content
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

disable use of stdext::checked_array_iterator for VS2019 and newer #309

Merged
merged 1 commit into from
Oct 8, 2024

Conversation

bashbaug
Copy link
Contributor

@bashbaug bashbaug commented Oct 3, 2024

Possible fix for #293.

It seems that the use of stdext::checked_array_iterator is not required for VS2019 and newer. So, add _MSC_VER checks to fall back to the generic version for newer versions of Visual Studio.

Copy link
Contributor

@MathiasMagnus MathiasMagnus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Checked back to VS 2015. 2015 (toolset v140) issues a false warning on /W4, but we can't fix that. (I argues about an unreferenced formal parameter to a function, but the parameter is totally used. No ifdefs, no control flow...) This change however seems fine. Toolsets v141, v142, v143 all pass warning free.

@bashbaug bashbaug merged commit 5d0123c into KhronosGroup:main Oct 8, 2024
52 checks passed
@bashbaug bashbaug deleted the ci-fixes-msvc branch October 8, 2024 17:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants