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

Removed Less-Simple Uses of STD Iterator #2561

Conversation

AlexandreSinger
Copy link
Contributor

See issue #2557 for context.

As with PR #2558 , removed slightly more complicated uses of std::iterator after discussing this more.

This PR modifies Tatum, I will upstream these changes back to the Tatum library after the PR is merged.

After this PR, the only use of std::iterator would be in the Capnproto library, which may be quite a bit more complicated to resolve.

This also remove a strange alias used called "my_iter" which, according
to the comment, was used to avoid potential ambiguity in the Clang
compiler. I am not sure what this means, but I think it should be less
ambiguous when we no longer inheret from std::iterator.
This also remove a strange alias used called "my_iter" which, according
to the comment, was used to avoid potential ambiguity in the Clang
compiler. I am not sure what this means, but I think it should be less
ambiguous when we no longer inheret from std::iterator.
@AlexandreSinger
Copy link
Contributor Author

@vaughnbetz This has passed CI, I have verified that the warnings for these uses of std::iterator are now gone. These are all of the uses of std::iterator that VTR is responsible for. The rest of the uses can be resolved by upgrading capnproto and Yosys.

@vaughnbetz
Copy link
Contributor

Thanks!

@vaughnbetz vaughnbetz merged commit f523a0f into verilog-to-routing:master May 27, 2024
53 checks passed
@AlexandreSinger AlexandreSinger deleted the feature-remove-std-iterator branch May 27, 2024 21:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants