The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
The switch to use spdlog was focused on implications for the underlying implmentation not for changing the user API. You can read more at https://github.com/ros2/rcl_logging/pull/17
The user API specifically doesn't expose spdlog or any other logging implementation through it's abstraction so that the implementation can be changed without requiring users to change their code. As you noticed we already took advantage of this to switch to spdlog. And in the future we could consider changing the default. But right now it's possible for a system integrator to swap out the logging mechanism for specific deployments too.
We have kept it as simple as possible and do not want to require the use of one specific formatting technology. As the user may want to user a different formatting tool than fmtlib.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
