-
Notifications
You must be signed in to change notification settings - Fork 127
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
Improve message generation #11
Comments
I can't speak for other client libraries, but definitely can for rclpy. rclpy hasn't worked around this issue, it just happens to be included upstream, but there are no mechanisms in rclpy for not regenerating messages.
Could you file a ticket with an example so we can address this? Thanks. |
I'm not sure if we should try to do something about this (not sure if it's possible?), or simply hope we'll get included into ROS 2 proper and have The other points in this issue have been addressed, I think. |
@esteve what do you think about my previous comment? Can this issue be closed as "won't fix until rosidl_generator_rs is included in the ROS 2 distribution?" |
Having to include and recompile all the message types any rust project requires is kind of a non-starter:
Are there anyways we can improve upon this, like upstreaming
rosidl_generator_rs
as one of the default IDL generators, or reusing IDL files generated fromrosidl_generator_c
? How have other client libraries such asrclpy
worked around this? Are there memory safety considerations we should account for? Already I've encountered memory leaks using rclrs that could have been prevented by rustc and RAII.The text was updated successfully, but these errors were encountered: