Skip to content
New issue

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

Call trace information in exceptions #92

Open
Idorobots opened this issue Mar 13, 2021 · 1 comment
Open

Call trace information in exceptions #92

Idorobots opened this issue Mar 13, 2021 · 1 comment

Comments

@Idorobots
Copy link
Owner

It would really ease up debugging if the current continuation also contained a call trace up to that point - each &apply invocation should extend it with the closure metadata, while each scope exitting continuation automatically removes the topmost value.

@Idorobots
Copy link
Owner Author

A faster solution is to keep a ring buffer of recent call frames in memory - &apply then just pushes a frame into the call trace and then executes it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant