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

Speed up long stack traces #51

Open
ChrisCinelli opened this issue Sep 1, 2018 · 0 comments
Open

Speed up long stack traces #51

ChrisCinelli opened this issue Sep 1, 2018 · 0 comments

Comments

@ChrisCinelli
Copy link

I am still using this puppy... and I am still an happy customer.

I was looking at the implementation of the long stack traces. It looks like that you do string concatenations for each async stack.

I was wondering... Would not be better to just store a reference to the string and lazy concatenate the strings only when somebody access to the err.stack ? I think you can save a lot of CPU and memory this way.

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

No branches or pull requests

1 participant