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.
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
Fix compile probe and nightly backtraces #160
Fix compile probe and nightly backtraces #160
Changes from 3 commits
f80de3e
92b6a57
3d7b20d
dacfb55
dd05aa3
87ee15e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Per #121, some folks will continue to be unhappy about enforcing unstable features whenever we detect nightly. IIRC we discussed a while ago that we want to accomodate that use case. It doesn't make it any worse so I think it's fine to put that work off, but I thought it was worth mentioning.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, not wanting to break existing behavior in a "fix" PR, but rather make existing up to date nightly a tricky beast when it comes to libraries.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What was your motivation for rewriting this file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not your code / out of scope: We're getting a couple dead code errors in this file with DisplayError and NoneError. I'm surprised they're triggered even though we marked them public. Why don't we tag these structs as
#[allow(dead_code)]
?I am similarly distressed by the other warnings we get a dozen copies of down below. I thought the missing_doc_code_examples thing was resolved ages ago.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pub
in a private module can still be dead code.pub(crate)
is not even public, though.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I understand that. I guess my surprise is that it's existing code that's had attention paid to its visibility and yet it's dead. I'll find the last time it wasn't dead code and figure its story out.
Check warning on line 5 in eyre/src/wrapper.rs
GitHub Actions / Test Suite (beta, --no-default-features --features track-caller)
Check warning on line 5 in eyre/src/wrapper.rs
GitHub Actions / Test Suite (beta, --no-default-features)
Check warning on line 5 in eyre/src/wrapper.rs
GitHub Actions / Test Suite (beta, --no-default-features --features auto-install)
Check warning on line 5 in eyre/src/wrapper.rs
GitHub Actions / Test Suite (nightly, --no-default-features --features track-caller)
Check warning on line 5 in eyre/src/wrapper.rs
GitHub Actions / Test Suite (nightly, --no-default-features --features auto-install)
Check warning on line 5 in eyre/src/wrapper.rs
GitHub Actions / Test Suite (nightly, --no-default-features)
Check warning on line 13 in eyre/src/wrapper.rs
GitHub Actions / Test Suite (beta, --no-default-features --features track-caller)
Check warning on line 13 in eyre/src/wrapper.rs
GitHub Actions / Test Suite (beta, --no-default-features)
Check warning on line 13 in eyre/src/wrapper.rs
GitHub Actions / Test Suite (beta, --no-default-features --features auto-install)
Check warning on line 13 in eyre/src/wrapper.rs
GitHub Actions / Test Suite (nightly, --no-default-features --features track-caller)
Check warning on line 13 in eyre/src/wrapper.rs
GitHub Actions / Test Suite (nightly, --no-default-features --features auto-install)
Check warning on line 13 in eyre/src/wrapper.rs
GitHub Actions / Test Suite (nightly, --no-default-features)