Adnan Ademovic

Does this build for messages that have fixed arrays of very long length? For example, `geometry_msgs/TwistWithCovariance`.

I've explained in #137 that the new dynamic data format can be used to work with serde.

Ideally, of course, ROS would have crates generated in their build system, which is something I considered, but the work of integrating that feels overwhelming, and once it's out there...

Btw, your `rosmsg list` idea is really good and has a lot of merit. I never even thought about the fact that ROS allows you to just list all the...

It's a tradeoff. Either have ROS installed, or manually create a `ROSRUST_MESSAGE_TYPES` or whatever named environment variable that will contain what you would have wanted `rosmsg list` to print if...

That's the idea, yes. That allows you to not have ROS installed and still depend on crates that depend on `rosrust-messages`. There is a lot to consider though with this...

All the triggers seem to work nicely, and I've added support for a comma separated list of message types to be provided in the discussed env variable. I'll look a...

I've removed support for the env variable. Instead we just crawl for all messages in the path manually.

I never looked into the internals of TF/TF2, so I have no design in mind. It's is just a separate library, so it is something that you could work on...

Looks good, thanks! I've been on a bit of a hiatus, contributions are appreciated.