Don't define member functions inside a nested namespace #113
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.
This trips up MSVC, in that member functions aren't properly included in the object files of the various translation units.
e.g.
DumpBin
ofsymbol_table.lib
:Generally, this can be fixed by having a
using
declaration in a .cpp file to enable the namespace. From my experience, a general good practice is to never nest definitions in namespaces, unless the namespace is only visible from within a translation unit (e.g. adetail
namespace inside a .cpp file).This doesn't fix all of the places in the code where this pattern is used - only the (narrow) compile path that i've been excercising. Someone should probably go through the rest of the codebase and apply this - will be needed if/when a windows CI pipeline is added.