Use std::backtrace #184
Closed
Use std::backtrace #184
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stefnotch
commented
Oct 12, 2023
Author
There was a problem hiding this comment.
I can also remove this file again, it was mainly for testing the backtrace feature.
On that note, I'd love it if there were a visualizer example that displayed backtraces.
Jasper-Bekkers
approved these changes
Nov 2, 2023
Author
|
Closing in favour of #186 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Supersedes #183 . I picked
Option<Arc<Backtrace>>, which shouldn't have any overhead, as long as the backtrace flag is not set.I also bumped up the Rust edition, since the backtrace was added in Rust 1.65.0, which has been released well after the Rust 2021 edition has been released.