With this change, someone using swri_roscpp's publishers or subscribers will be able to put subscriptions into a non-default callback group or turn on intraprocess communications at the pub/sub level, along with some other configuration features.
I currently have the SubscriptionOptions as the last argument, but if we think that argument is more likely to be used / required than the transport hints / QoS, then I can flip them.
With this change, someone using
swri_roscpp's publishers or subscribers will be able to put subscriptions into a non-default callback group or turn on intraprocess communications at the pub/sub level, along with some other configuration features.I currently have the
SubscriptionOptionsas the last argument, but if we think that argument is more likely to be used / required than the transport hints / QoS, then I can flip them.