2 ms·
> If so can you now understand why you would want to be alerted about a new exception getting thrown at compile-time as well? The library code can already thro
by mrkeen 3y ago
> If so can you now understand why you would want to be alerted about a new exception getting thrown at compile-time as well?
The library code can already throw anything. OutOfHeap, over/underflow, div0, stackoverflow, threadinterrupted. The caller already knows the function can throw, and documenting one more flavour of throw doesn't tell the caller anything.
- twelve40 3y ago> documenting one more flavour of throw doesn't tell the caller anything but it does, in cases when there are errors that can or should be retried. Like a whitelist of documented cases where recovery and retry are possible, and of course all this infinite runtime stuff that can happen unexpectedly, for which there is no immediate solution.