Logger and error handling strategy

[budrus]

Brief feature description

Having a clear strategy for logging and error handling

Detailed information

• initial document for logging and error handling strategy

• clarification of open points like error handling in utils

  • How to deal with terminate(), assert, expects() etc.?

[MatthiasKillat]

While we have error-handling.md which summarizes our current error handling strategy and mentions open points (cf. #343)

How do specifically deal with errors in iceoryx::utils is not addressed in much detail there (we have yet to find a clear strategy for this).

@budrus
I propose to leave this issue open but maybe rename the issue to Logger and error handling strategy in iceoryx::utils.

Even if we do not want to do this, we have not yet verified that all methods are indeed noexcept.

[budrus]

@MatthiasKillat OK, but this is then no more a topic for the 1.0 release. I will update the description

[mossmaurice]

How to deal with terminate(), assert, expects() etc.?

This is solved in the error handling document.

Do not use std::terminate directly but use assert-like constructs such as Expects or Ensures.

Hence, closing this issue.