You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
@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?
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.
The text was updated successfully, but these errors were encountered: