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

Add yaml_read_archive suport #10869

Closed
jwnimmer-tri opened this issue Mar 8, 2019 · 2 comments · Fixed by #10954
Closed

Add yaml_read_archive suport #10869

jwnimmer-tri opened this issue Mar 8, 2019 · 2 comments · Fixed by #10954

Comments

@jwnimmer-tri
Copy link
Collaborator

Anzu has a component named yaml_read_archive, which uses the visitor/archive pattern to easily load yaml data into C++ structures, without having to write boilerplate.

Its API and implmentation seem stable enough now that we should relocate this component to Drake, so it can be used where Drake needs to touch YAML data.

@jwnimmer-tri
Copy link
Collaborator Author

@sammy-tri My proposed plan would be thus: PR the Anzu files into a dev folder in Drake (tests and all) without any changes; this should be a rubber-stamp PR, since the code has already been feature-reviewed. Then, use Drake PR(s) to finish any TODOs or warts, and then platform-review its move out of dev. Does that sounds good, or too complicated?

@sammy-tri
Copy link
Contributor

Sounds reasonable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants