-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Rewrite "prepareStackTrace" to use Rust API #7644
Comments
kitsonk
added
cli
related to cli/ dir
deno_core
Changes in "deno_core" crate are needed
feat
new feature (which has been agreed to/accepted)
labels
Sep 25, 2020
bnoordhuis
added a commit
to bnoordhuis/rusty_v8
that referenced
this issue
Jan 21, 2021
bnoordhuis
added a commit
to bnoordhuis/rusty_v8
that referenced
this issue
Feb 7, 2021
bnoordhuis
added a commit
to denoland/rusty_v8
that referenced
this issue
Feb 8, 2021
With recent improvements to error handling by @nayeemrmn done in #14378, #14394, #14302 and #14274 I feel this issue is no longer of high importance. Closing for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently CLI uses
Error.prepareStackTrace
API to perform source mapping and formatting of errors.This situation leads to overall complexity of this method as well as requirement to manually acquire information about stack frames as well as distributing the logic between JS and Rust.
We want to avoid jumping between JS and Rust as much as possible and to solve this problem in this situation we need to:
StackFrame
to acquire the same data as usingCallSite
:deno/cli/rt/40_error_stack.js
Lines 172 to 191 in d68fb81
prepareStackTrace
method fromcli/rt/40_error_stack.js
and instead useIsolate::set_prepare_stack_trace_callback
- needs to be added torusty_v8
firstCC @ry @nayeemrmn
The text was updated successfully, but these errors were encountered: