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

Avoid possible namespace clash for fmt #1522

Merged
merged 1 commit into from
Jan 15, 2020
Merged

Conversation

lefticus
Copy link
Contributor

Problem

In the case of an existing fmt namespace (in my project this looks like Project::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.

## Problem

In the case of an existing `fmt` namespace (in my project this looks like `Project::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`
lefticus added a commit to NREL/EnergyPlus that referenced this pull request Jan 15, 2020
@mjwitte I believe this is the correct solution instead of chasing down
potential conflicts over and over.

I've submitted a patch to {fmt} fmtlib/fmt#1522
@vitaut vitaut merged commit 4ccbe4b into fmtlib:master Jan 15, 2020
@vitaut
Copy link
Contributor

vitaut commented Jan 15, 2020

Thanks!

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