Don't expose ::util:: symbols
#10
Assignees
Labels
Task
Something to be done in the codebase which does not fix a bug and does not enhance it per se.
Comments
eyalroz
added
the
Task
eyalroz
pushed a commit
that referenced
this issue
Feb 3, 2020
Workaround for exposed `::util::` symbols in the installed library - hoping for a better solution!
eyalroz
pushed a commit
that referenced
this issue
Feb 3, 2020
…rfering with code outside the library. Note: This is a Workaround for exposed `::util::` symbols in the installed library - hoping for a better solution!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our library currently exposes symbols in the
::util::namespace, which are only used internally. That shouldn't happen - others might want to use those names.Here's an SO question about this issue..
For now, let's use a workaround - move a lot of the utility code into a nameapace - avoiding accidental dependencies by outside source but not making the symbols actually private.
The text was updated successfully, but these errors were encountered: