Reevaluate the const-ness of the classes and interfaces to rcl
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 805
- Forks
- 564
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 27
Description
Bug report
Over in https://github.com/ros2/rclcpp/pull/1119#discussion_r432041729 , we had a bit of a discussion about the const-ness of interfaces, particularly how it relates to how rclcpp interfaces with rcl. After that discussion, it seems like there may be some constness problems in that interface. We should re-evaluate how constness is used, particularly at the rcl interface boundary.
Required Info:
- Operating System:
- Ubuntu 20.04
- Installation type:
- Source
- Version or commit hash:
- 87bb9f9758dce239d37256ae91d58ce6325f405b
- DDS implementation:
- Fast-RTPS
- Client library (if applicable):
- rclcpp
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 reading the constness discussion in the linked rclcpp pull request, then trace the rclcpp interface boundary referenced in the issue. The issue does not name files or tests; done requires an agreed assessment of const usage and corresponding interface changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend-api-design
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100