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
Currently, we only support convert functions to go between custom and ROS message types, which are more efficient for intra-process communication. It would be more efficient (less copy operations) for inter process communication to support serialization and deserialization functions.
I've put this issue on the H-turtle board for consideration.
The text was updated successfully, but these errors were encountered:
audrow
changed the title
Support Serialize/deserialize functions in Type Adaption
Support Serialize/Deserialize Functions in Type Adaption
May 13, 2021
No, it would not. That's orthogonal to this issue which is supporting (de)serialization of custom types directly to/from the wire format. It doesn't cover other targets like yaml and it doesn't cover that for existing ROS types, only the custom types (which don't have to_yaml() either atm).
Currently, we only support convert functions to go between custom and ROS message types, which are more efficient for intra-process communication. It would be more efficient (less copy operations) for inter process communication to support serialization and deserialization functions.
I've put this issue on the H-turtle board for consideration.
The text was updated successfully, but these errors were encountered: