On Aug 7, 2013 1:33 PM, "Jonathan S. Shapiro" <[email protected]> wrote: > Why on earth would you ever be copying the stack?
What scope should the stack backtrace be valid for? Once a finally block runs (potentially calling a function), the stack is modified so the original stack has been overwritten. In practice, I've had even more trouble with the performance of CLR exceptions while running under a debugger. Even when the exceptions are caught, they put a massive toll on performance. This seems implementation defined and fixable. Backing out of the CLR details.. Bennie, all I want is a fast structured error handling mechanism which includes assignment analysis. I don't much care is there is another slow one. I'm happy to ignore it. The issue I have with slow exception handling is that it generally forces me into choosing between fast less-safe code with no assignment analysis; or slow safer code with exceptions. That's a bad deal in my book.
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
