We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The exception type needs support for stack traces. When an exception is thrown, the N topmost tiro function names should be represented in the trace.
Exact positions within those functions (e.g. line numbers) are currently out of scope because the compiler does not yet emit those information.
The text was updated successfully, but these errors were encountered:
Implement simple exception stack traces (closes #18)
67c6f02
If panic stack traces are enabled (a flag during vm construction, off by default), a very simple stack trace is attached to every exception.
The stack trace reflects function names only at the moment.
Example:
import std; export func test() { nested(2); } func nested(n) { if n == 0 { std.panic("help!"); } nested(n - 1); }
Calling test produces the following trace (most nested function on top):
Coroutine-1: - nested - nested - nested - test
Sorry, something went wrong.
Note: module names etc. are currently not part of the function name. Modules are not fleshed out well, yet.
b19478d
No branches or pull requests
The exception type needs support for stack traces.
When an exception is thrown, the N topmost tiro function names should be represented in the trace.
Exact positions within those functions (e.g. line numbers) are currently out of scope because the compiler does not yet emit those information.
The text was updated successfully, but these errors were encountered: