Capability to destroy single ports in the shared memory individually and not only all together when cleaning up the whole user process.
Detailed information
Today, when publishers and subscribers are destroyed, the shared memory resources are not cleaned up. This is done when the whole process is cleaned up, i.e. when the process is terminated.
For better supporting systems like ROS where publishers and subscribers can be flexibly created and destroyed within the process lifetime, iceoryx must be extended to allow destroying shared memory resources like ports individually.
Runnable cleanup will be done in a separate refactoring. So this issue only does the cleanup of sender and receiver ports which is required to get the ROS2 python API running
Brief feature description
Capability to destroy single ports in the shared memory individually and not only all together when cleaning up the whole user process.
Detailed information
Today, when publishers and subscribers are destroyed, the shared memory resources are not cleaned up. This is done when the whole process is cleaned up, i.e. when the process is terminated. For better supporting systems like ROS where publishers and subscribers can be flexibly created and destroyed within the process lifetime, iceoryx must be extended to allow destroying shared memory resources like ports individually.