2 ms·
It is ABI breaking but there is a way out. Instead of replacing the existing exceptions, this mechanism could be used for checked exceptions only which will nec
by gpderetta 7y ago
It is ABI breaking but there is a way out. Instead of replacing the existing exceptions, this mechanism could be used for checked exceptions only which will necessarily require annotating functions, so ABI breaks are to be expected.
- aw1621107 7y agoWouldn't function annotations be an API break, too? And I'd imagine checked exceptions would get a decent amount of pushback due to Java's implementation.
- gpderetta 7y agoYes, but they are opt-in. I think, given the right abstraction capabilities they might work in C++. They are semantically no different than returning an either<T, error>.