diff options
| author | bors <bors@rust-lang.org> | 2019-09-11 14:46:08 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2019-09-11 14:46:08 +0000 |
| commit | fe6d05a8b32f5c66c427ca524dbcce5a7145f87e (patch) | |
| tree | 8c28b22f8fc089fa753c1359341bd67039d0f596 /src/test/ui/iterators/iter-sum-overflow-overflow-checks.rs | |
| parent | 74d5c70b174f06843049af2d764ff57ddc81c81c (diff) | |
| parent | 34662c69614028944668f96c91ef294e7da048f0 (diff) | |
| download | rust-fe6d05a8b32f5c66c427ca524dbcce5a7145f87e.tar.gz rust-fe6d05a8b32f5c66c427ca524dbcce5a7145f87e.zip | |
Auto merge of #64154 - alexcrichton:std-backtrace, r=sfackler
std: Add a `backtrace` module This commit adds a `backtrace` module to the standard library, as designed in [RFC 2504]. The `Backtrace` type is intentionally very conservative, effectively only allowing capturing it and printing it. Additionally this commit also adds a `backtrace` method to the `Error` trait which defaults to returning `None`, as specified in [RFC 2504]. More information about the design here can be found in [RFC 2504] and in the [tracking issue]. Implementation-wise this is all based on the `backtrace` crate and very closely mirrors the `backtrace::Backtrace` type on crates.io. Otherwise it's pretty standard in how it handles everything internally. [RFC 2504]: https://github.com/rust-lang/rfcs/blob/master/text/2504-fix-error.md [tracking issue]: https://github.com/rust-lang/rust/issues/53487 cc #53487
Diffstat (limited to 'src/test/ui/iterators/iter-sum-overflow-overflow-checks.rs')
0 files changed, 0 insertions, 0 deletions