-
-
Notifications
You must be signed in to change notification settings - Fork 406
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
[Merged by Bors] - Add limited console.trace implementation #1623
Conversation
|
||
#[cfg(not(feature = "vm"))] | ||
fn get_stack_trace(_: &mut Context) -> Vec<String> { | ||
vec![] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should leave a TODO
comment here so that it is easy to spot
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bors r+
This Pull Request partially fixes #307. It changes the following: - Implements limited `console.trace` functionality by dumping stack trace. Since `console.trace`'s output is supposed to be implementation-specific according to the technical specification, it should be technically correct 😀 Any hints about potential improvements are welcome!
This PR was included in a batch that was canceled, it will be automatically retried |
This Pull Request partially fixes #307. It changes the following: - Implements limited `console.trace` functionality by dumping stack trace. Since `console.trace`'s output is supposed to be implementation-specific according to the technical specification, it should be technically correct 😀 Any hints about potential improvements are welcome!
Pull request successfully merged into main. Build succeeded: |
This Pull Request partially fixes #307.
It changes the following:
console.trace
functionality by dumping stack trace. Sinceconsole.trace
's output is supposed to be implementation-specific according to the technical specification, it should be technically correct 😀 Any hints about potential improvements are welcome!