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

fix for backtrace 0.3.10 #282

Closed
wants to merge 2 commits into from
Closed

fix for backtrace 0.3.10 #282

wants to merge 2 commits into from

Conversation

RalfJung
Copy link

There's a Display instance now, so bt.fmt is ambiguous.

Cc rust-lang/rust#56718

@RalfJung
Copy link
Author

I don't understand why CI still fails, this PR now does not touch the lockfile?

@RalfJung RalfJung closed this Dec 11, 2018
@RalfJung RalfJung reopened this Dec 11, 2018
@RalfJung
Copy link
Author

I thought it might have been a cache thing but it wasn't.

@alexcrichton looks like backtrace doesn't work on Rust 1.18 any more, which breaks failure's CI.

@BurntSushi
Copy link

See #279, #280, #281

@RalfJung
Copy link
Author

Closing in favor of #279, which was first.

} else { Ok(()) }
}
}

impl Display for Backtrace {
fn fmt(&self, f: &mut fmt::Formatter) -> fmt::Result {
if let Some(bt) = self.internal.as_backtrace() {
bt.fmt(f)
Debug::fmt(bt, f)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RalfJung I think this should be Display.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That would require bumping the minimal version of backtrace, though.

And anyway I closed this PR because #279 does the same thing.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, yeah, I was trying to answer: #279 (comment)

But I didn't know about the minimal version requirement.

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

Successfully merging this pull request may close these issues.

None yet

2 participants