DataAlgo : Move to dedicated namespace - #1561
Open
johnhaddon wants to merge 2 commits into
Open
johnhaddon wants to merge 2 commits into
johnhaddon wants to merge 2 commits into
Conversation
With a `using` fallback so folks don't have to adapt right away. Technically this is still a source compatibility break though, as the USD changes show - it's possible for ambiguity to exist with pre-existing DataAlgo namespaces in other libraries.
johnhaddon
force-pushed
the
dataAlgoNamespace
branch
from
September 15, 2026 14:56
1ac468d to
ab69dc4
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I've been finding things like
IECore::size()andIECore::trait()kindof unobvious, and I think moving them to a namespace helps with that.