Workaround for known GCC bug regarding explicit specialization in non namespace scope #163
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
arekmula
force-pushed
the
fix-gcc-explicit-specialization-in-non-namespace-scope
branch
from
230fa8e
to
f3bbca2
Compare
li-feng-sc
reviewed
Feb 26, 2024
li-feng-sc
approved these changes
Feb 26, 2024
arekmula
force-pushed
the
fix-gcc-explicit-specialization-in-non-namespace-scope
branch
from
f3bbca2
to
bd84442
Compare
arekmula
deleted the
fix-gcc-explicit-specialization-in-non-namespace-scope
branch
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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey,
This is a workaround for a known bug in GCC.
Similar issue on StackOverflow