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

Support Serialize/Deserialize Functions in Type Adaption #1665

Open
audrow opened this issue May 11, 2021 · 3 comments
Open

Support Serialize/Deserialize Functions in Type Adaption #1665

audrow opened this issue May 11, 2021 · 3 comments
Labels
backlog enhancement New feature or request

Comments

@audrow
Copy link
Member

audrow commented May 11, 2021

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.

@audrow audrow added the enhancement New feature or request label May 11, 2021
@audrow audrow changed the title Support Serialize/deserialize functions in Type Adaption Support Serialize/Deserialize Functions in Type Adaption May 13, 2021
@asasine
Copy link

asasine commented Oct 22, 2021

Would this encompass deserializing a YAML representation of a message to its ROS/custom message type, the opposite of rosidl's to_yaml() function?

@audrow
Copy link
Member Author

audrow commented Oct 27, 2021

I'm not sure. I'm not very familiar with rosidl. Any thoughts, @wjwwood?

@wjwwood
Copy link
Member

wjwwood commented Nov 29, 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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants