Enhance ABI stability
Open
Nobody has claimed this yet.
backlog
enhancement
- Dominant language
- C++
- Stars
- 805
- Forks
- 564
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 27
Description
Feature request
Feature description
We have run many times in the issue of not being able to backport a fix because it would break ABI.
e.g.:
- https://github.com/ros2/rclcpp/pull/1119 is almost impossible to backport.
- https://github.com/ros2/rclcpp/pull/1056
Implementation considerations
We should evaluate where the effort matters and where it doesn't.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked pull requests, rclcpp/pull/1119 and rclcpp/pull/1056, to understand which backports were blocked by ABI changes. Then identify where ABI stability matters in rclcpp and document the areas worth addressing. Done means the scope and an implementation approach are agreed, since the issue currently asks for evaluation rather than naming a concrete change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- robotics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100