On Tuesday, 16 February 2021 at 00:39:33 UTC, Steven
Schveighoffer wrote:
On 2/15/21 4:04 PM, Jack wrote:
I have to make my function nothrow because the function that
calls it (not written by me) is nothrow. So I need to wrap my
code in a try-catch() but how will I report the error message,
On 2/15/21 4:04 PM, Jack wrote:
I have to make my function nothrow because the function that calls it
(not written by me) is nothrow. So I need to wrap my code in a
try-catch() but how will I report the error message, if the toString()
from Throwable isn't nothrow? how do I get out this
On 2/15/21 1:04 PM, Jack wrote:
> I have to make my function nothrow because the function that calls it
> (not written by me) is nothrow. So I need to wrap my code in a
> try-catch() but how will I report the error message, if the toString()
> from Throwable isn't nothrow? how do I get out this
On Monday, 15 February 2021 at 21:04:50 UTC, Jack wrote:
obviously, insert a try-catch() within catch() is a circular
dependence and doesn't solve the problem either (even if it, I
think it would be quite ugly)
well that's prolly the way to do it, just catch Exception and
like assert(0) if
I have to make my function nothrow because the function that
calls it (not written by me) is nothrow. So I need to wrap my
code in a try-catch() but how will I report the error message, if
the toString() from Throwable isn't nothrow? how do I get out
this circular dependence?
void f()
