Adnan Ademovic

I'm having the same issue to solve, in a simpler version. I don't know how I'd represent a structure that can accept either of these 3: ``` bar case_a case_b...

I worked with an enum of approximately this design: ``` rust enum foo { #[serde(rename="a")] A(String), #[serde(rename="b")] B(String), #[serde(rename="$value")] // added this V(String), // added this } ``` And it...

It might be better to make a separate library that uses async/await. The "thread for everything" approach is what is done in the official ROS clients. Working with async/await forces...

Why not drop all of ROS in lazy_static? Why just the logger? I feel like it's a more elegant solution.

I meant setting `ROS = None`, instead of `ROS.logger = None` That way we do drop. I think this is just a Rust language issue we need to handle. Maybe...

This might be totally unrelated, but you're not doing anything with the `Result` returned by `try_init_with_options`. You might be even getting an issue there. I also recommend setting up some...

This is because everything is running in parallel, like in `rospy`, rather than a hybrid of channels in parallel and an event loop in the same thread as the node's...

That would be great! I've posted [a question](http://answers.ros.org/question/251215/what-do-getbusstats-and-getbusinfo-exactly-return/) on ROS Answers to see if anyone could give me any clues. There were questions before, but nobody answered them.

Too bad. Still greatly appreciated. As mentioned in my question, even officially distributed client libraries just put a "TODO" there, so I did the same for now, and I've put...

I'm not sure how that relates to these two API methods. But it they're deprecating those things, then great. This node handle thing seems interesting by itself. I've made something...