Make Sdf_LayerRegistry::FindByIdentifier private
#2592
Merged
Conversation
This file contains 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
|
Filed as internal issue #USD-8591 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of Change(s)
Layer identifiers when multiple contexts are bound are not guaranteed to be unique. As such,
FindByIdentifiermay not return the intended result. It's only used once externally (in aTF_VERIFYstatement). This updates that statement to useFindwith an explicitly resolved path and makesFindByIdentifierprivate.Simplifying the public API for
Sdf_LayerRegistrywill help the boost removal effort by scoping what kind of queries the replacement data structure needs to support.Fixes Issue(s)