VS2017 compiler workaround #2030
Merged
Conversation
… where the variadic templates would not compile correctly. Issue should be patched in future versions, so for now it'll target the 1910 version specifically.
|
Ah Visual Studio. Still the only compiler that requires dodgy workarounds. ;) #MakeTemplatesGreatAgain |
|
Also should tag this issue #1969 |
Areloch
added a commit
to Areloch/GG-Torque3D
that referenced
this pull request
Jun 7, 2020
VS2017 compiler workaround
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Works around the regressive behavior in the VSC++ compiler for VS2017 where the variadic templates would not compile correctly. Issue should be patched in future versions, so for now it'll target the 1910 version specifically.