That is, the ROS node has-a Driver variable, instead of is-a Driver.
This would encourage better decoupling of the code, especially when there are multiple contributors. Submissions will often hack at the top level (ROS wrapper) rather than trying to dive into the Driver internals. it was a bit of a tangle in ROS1.
Wouldn't otherwise provide any benefit though, so nice-to-have only.
That is, the ROS node has-a Driver variable, instead of is-a Driver.
This would encourage better decoupling of the code, especially when there are multiple contributors. Submissions will often hack at the top level (ROS wrapper) rather than trying to dive into the Driver internals. it was a bit of a tangle in ROS1.
Wouldn't otherwise provide any benefit though, so nice-to-have only.