[ros-users] [Discourse.ros.org] [Next Generation ROS] Design By Contract

Davide Faconti ros.discourse at gmail.com
Tue Aug 8 20:58:16 UTC 2017

My two cents.
It sound to be a good idea, if a missing requirement genrate a warning, rather than an assertion/exception.

Some of the things you described seems to be related more to Quality of Services, rather than Design by Contract, but I might be wrong.

The more I learn modern C++, more I realize that the best "contracts" can be usually implemented using "strong types".
I am in favour of using something similar to __boost::units__ in ROS messages, some kind of metadata attached to the topic itself that is NOT transmitted every time and is immutable. 

But I am aware that this is another topic...

[Visit Topic](https://discourse.ros.org/t/design-by-contract/2405/2) or reply to this email to respond.

More information about the ros-users mailing list