Shane Snover

Add support for parsing the remaining fields in the Connection Header

1

Currently missing a couple (see `tcpros.rs`), however I didn't see these in the packet capture coming from the subscriber node so they're documented but maybe unused in practice.

Currently a garden-variety string literal is used, and the tokenization process escapes characters including new-lines in a single unbroken line. Using a raw-string literal here would be easier to read.

ROS1: Work needed to support native ROS1 nodes

1

Did a little spelunking through ros/ros_comm some time ago and I think the things needed to achieve basic pubsub on ROS1 are: * Start generating md5sums for message types and...

Request to add to roadmap: logging to rosconsole

1

Would be great to have a `log` compatible backend log driver that used the normal ROS mechanism as part of this crate.

Just a tiny MR to help potential contributors and users who aren't as familiar with the C++ SDK (#149)

Strange Output In Disassembled Binary

2

Hello, I've been working on trying out Rust on the MSP430 Launchpad. I'm currently working through a bug and so I've been looking through the disassembly. Among the output from...

Hello, Would you accept a PR for a function for parsing a string to build an XML request? I'm looking to create an XML server and would like to leverage...