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

Replace boost::iterator_adaptor with explicitly specified iterator definition for UsdNotice::ObjectsChanged::PathRange #2269

Merged
merged 1 commit into from
Aug 16, 2023

Conversation

nvmkuruc
Copy link
Collaborator

@nvmkuruc nvmkuruc commented Feb 13, 2023

Description of Change(s)

  • Introduces an _UnderlyingIterator type alias for _PathsToChangesMap::const_iterator in UsdNotice::ObjectsChanged::PathRange::iterator
  • Explicitly implement the equality, increment, dereference, and arrow operators for UsdNotice::ObjectsChanged::PathRange::iterator
  • Add GetBase method to the iterator for direct query of the underlying iterator

Fixes Issue(s)

  • I have verified that all unit tests pass with the proposed changes
  • I have submitted a signed Contributor License Agreement

@tallytalwar
Copy link
Contributor

Filed as internal issue #USD-8007

@@ -171,15 +194,22 @@ class UsdNotice {
/// details.
USD_API bool HasChangedFields() const;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per our discussion, it'll be better to include a deprecated base() function that returns the underlyingIterator to maintain downstream compatibility in the meantime.

…definition for `UsdNotice::ObjectsChanged::PathRange`
@pixar-oss pixar-oss merged commit 7d7a634 into PixarAnimationStudios:dev Aug 16, 2023
@nvmkuruc nvmkuruc deleted the usdnoticeadaptor branch December 29, 2023 03:14
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.

5 participants