| 118 | } |
| 119 | |
| 120 | Connection::~Connection() |
| 121 | try |
| 122 | { |
| 123 | Connection::leaveEventLoop(); |
| 124 | } |
| 125 | catch (...) // NOLINT(bugprone-empty-catch) |
| 126 | { |
| 127 | // Theoretically, we can fail to notify the event fd or join with the joinable thread... |
| 128 | // What to do now here in the destructor? That is the question: |
| 129 | // 1. Report the problem... but how, where? |
| 130 | // 2. Terminate immediately... too harsh? |
| 131 | // 3. Ignore and go on... even when some resources may be lingering? |
| 132 | // Since the failure here is expected to be very unlikely, we choose the defensive approach of (3). |
| 133 | } |
| 134 | |
| 135 | void Connection::requestName(const ServiceName& name) |
| 136 | { |
nothing calls this directly
no outgoing calls
no test coverage detected