Grey
Grey
In the meantime @montmejat you can refer to the examples [here](https://github.com/ros2-rust/ros2_rust/tree/main/examples/minimal_pub_sub/) which are up to date.
Let's reopen the issue to keep it tracked. This is something we should get fixed.
Client and service examples can be found [here](https://github.com/ros2-rust/ros2_rust/tree/main/examples/minimal_client_service). We might want to consider consolidating all the examples.
Help is always appreciated, thanks for offering @roboticswithjulia ! [This page](https://doc.rust-lang.org/rustdoc/how-to-write-documentation.html) provides a quick overview of how documentation works in Rust. The key thing is that when you use ```...
This is an interesting idea. But it's such an unconventional use of crates.io and cargo that I'd need to think very carefully about potentially bad side effects. Would we also...
Closed by #386
> I think one of the difficulties of deriving traits for message types is that we have very little information about the individual messages before compile time. We cannot be...
> Is there a specific reason that you would like to see these traits automatically derived? I'm strongly in favor of providing the implementations for the sake of developer quality...
All that said, I might suggest we save traits for a follow up PR.
> Certain of these methods involve accessing timestamps and UUIDs in messages. To avoid adding a dependency in rosidl_runtime_rs on builtin_interfaces and unique_identifier_msgs, these are represented in a more primitive...