Skip to content
This repository has been archived by the owner on Aug 16, 2021. It is now read-only.

backtrace name collision #270

Open
AndyGauge opened this issue Sep 20, 2019 · 1 comment
Open

backtrace name collision #270

AndyGauge opened this issue Sep 20, 2019 · 1 comment

Comments

@AndyGauge
Copy link
Contributor

AndyGauge commented Sep 20, 2019

https://travis-ci.com/rust-lang-nursery/error-chain/jobs/240939141#L293

error: a method with this name may be added to the standard library in the future

--> src/lib.rs:657:41

|

657 | if let Some(backtrace) = self.0.backtrace() {

|                                         ^^^^^^^^^

|

= note: `-D unstable-name-collisions` implied by `-D warnings`

= warning: once this method is added to the standard library, the ambiguity may cause an error or change in behavior!

= note: for more information, see issue #48919 <https://github.com/rust-lang/rust/issues/48919>

= help: call with fully qualified syntax `ChainedError::backtrace(...)` to keep using the current method

= help: add `#![feature(backtrace)]` to the crate attributes to enable `std::error::Error::backtrace`
@palfrey
Copy link
Contributor

palfrey commented Dec 4, 2019

This should be fixed by #279

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

No branches or pull requests

2 participants