-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add keys
to ModuleManager
#326
Conversation
The docs build test can be fixed by setting |
Thanks @jwaldrop107, added. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple of minor tweaks and then this is r2g!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This LGTM after you drop the noexcept
qualifiers from keys
.
Co-authored-by: Ryan Richard <[email protected]>
Co-authored-by: Ryan Richard <[email protected]>
Co-authored-by: Ryan Richard <[email protected]>
🚀 [bumpr] Bumped! New version:v1.0.17 Changes:v1.0.16...v1.0.17 |
PR Type
Brief Description
My intention was to enable iteration for
ModuleManager
in Python. The python bindings required for that is commented out in this PR as it is throwingdouble free or corruption (out)
when tested.Instead of that this PR adds
keys
method as suggested by @jboschen to return a vector of keys for the ModuleManager and python bindings for__getitem__
to enable accessing the modules with[]
using the key.Not In Scope
PR Checklist