Przemysław Dąbrowski

Can w discuss an idea of logging API? Even empty interfaces would unblock work on #167.

I don't feel to propose an idea other than making something similar to rclcpp. Anyway I think, that making macros (I suppose they will be used like in rclcpp) design...

Should `rcl` be used in implementation? Also `log` crate doesn't have `FATAL` severity while `rcl` does. As far as I can see both [rclpy](https://github.com/ros2/rclpy/blob/rolling/rclpy/src/rclpy/logging.cpp) and [rclcpp](https://docs.ros2.org/latest/api/rclcpp/logging_8hpp.html#a28cf59074387c81ef082f3e774481e95) use `rcl` logging.

I'm using Foxy.

Depending on which approach would be chosen (warn or error) there should be logging (#184) implemented before or not. In case of warn prompting, logging mechanism is necessary, since error...

> Should they be `const` or `static` on the Rust side? Is there any reason, why they should be `static` instead of `const`?

Hi, I'm considering contribution to this issue. However, I need some hints how to start. AFAIK [this](https://github.com/ros2-rust/ros2_rust/blob/3b6c01364f2fd068d6c2049e102e26ff26fe4277/rclrs/src/subscription.rs#L186) and [this](https://github.com/ros2-rust/ros2_rust/blob/3b6c01364f2fd068d6c2049e102e26ff26fe4277/rclrs/src/subscription.rs#L190) Box::new functions have to be replaced with another one (which? [from_raw](https://doc.rust-lang.org/std/boxed/struct.Box.html#method.from_raw)?)....