ros2 / ros2/rclcpp

Support Serialize/Deserialize Functions in Type Adaption

Open
#1,665 3 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

backlog enhancement
Dominant language
C++
Stars
805
Forks
564
Avg merge
1d 17h
Merged PRs (30d)
27

Description

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files or tests. Start by tracing the existing convert-function support for custom and ROS message types, then clarify the API and scope for serialization and deserialization in inter-process communication. Done means both functions are supported alongside the current conversion functions.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.