Avoid possible namespace clash for fmt #1522
Merged
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.
Problem
In the case of an existing
fmt
namespace (in my project this looks likeProject::fmt
) it is possible to get a namespace clash in debug builds (MSVC 2017)Proposed Solution
When referencing
fmt
internally, be explicit that it is relative to the global namespace using::fmt
I agree that my contributions are licensed under the {fmt} license, and agree to future changes to the licensing.