-
-
Notifications
You must be signed in to change notification settings - Fork 150
Comparing changes
Open a pull request
base repository: dtolnay/anyhow
base: 1.0.66
head repository: dtolnay/anyhow
compare: 1.0.68
- 17 commits
- 9 files changed
- 1 contributor
Commits on Oct 20, 2022
-
Remove 2 frames of backtrace noise on Option's Context impl
Repro: use anyhow::Context; fn main() -> anyhow::Result<()> { let result = None::<()>; result.context("...") } Before: 0: anyhow::context::<impl anyhow::Context<T,core::convert::Infallible> for core::option::Option<T>>::context::{{closure}} at /git/anyhow/src/context.rs:95:57 1: core::option::Option<T>::ok_or_else at /rustc/4b8f4319954ff2642690b9e5cbe4af352d095bf6/library/core/src/option.rs:1083:25 2: anyhow::context::<impl anyhow::Context<T,core::convert::Infallible> for core::option::Option<T>>::context at /git/anyhow/src/context.rs:95:9 3: testing::main at ./src/main.rs:5:5 After: 0: anyhow::context::<impl anyhow::Context<T,core::convert::Infallible> for core::option::Option<T>>::context at /git/anyhow/src/context.rs:99:54 1: testing::main at ./src/main.rs:5:5
Configuration menu - View commit details
-
Copy full SHA for a8649ac - Browse repository at this point
Copy the full SHA a8649acView commit details -
Merge pull request #280 from dtolnay/contextbacktrace
Remove 2 frames of backtrace noise on Option's Context impl
Configuration menu - View commit details
-
Copy full SHA for 47e902a - Browse repository at this point
Copy the full SHA 47e902aView commit details -
Raise required compiler to rust 1.39
This is required for attributes on function parameters, which I hope to use for #[track_caller] / Location support: unsafe fn construct<E>( error: E, vtable: &'static ErrorVTable, backtrace: Option<Backtrace>, #[cfg(track_caller)] location: &'static Location<'static>, ) -> Self where E: StdError + Send + Sync + 'static;
Configuration menu - View commit details
-
Copy full SHA for cccc785 - Browse repository at this point
Copy the full SHA cccc785View commit details -
Configuration menu - View commit details
-
Copy full SHA for 3d2b6a3 - Browse repository at this point
Copy the full SHA 3d2b6a3View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0b42fed - Browse repository at this point
Copy the full SHA 0b42fedView commit details
Commits on Oct 21, 2022
-
Merge pull request #281 from dtolnay/redundantprovide
Remove redundant Backtrace provide_ref from ContextError
Configuration menu - View commit details
-
Copy full SHA for 6874b52 - Browse repository at this point
Copy the full SHA 6874b52View commit details -
Configuration menu - View commit details
-
Copy full SHA for fd34155 - Browse repository at this point
Copy the full SHA fd34155View commit details
Commits on Nov 11, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 451651b - Browse repository at this point
Copy the full SHA 451651bView commit details
Commits on Nov 16, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 8d1c734 - Browse repository at this point
Copy the full SHA 8d1c734View commit details
Commits on Nov 23, 2022
-
Fix renamed let_underscore_drop lint
warning: lint `clippy::let_underscore_drop` has been renamed to `let_underscore_drop` --> tests/test_ensure.rs:8:5 | 8 | clippy::let_underscore_drop, | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use the new name: `let_underscore_drop` | = note: `#[warn(renamed_and_removed_lints)]` on by default
Configuration menu - View commit details
-
Copy full SHA for 60e8800 - Browse repository at this point
Copy the full SHA 60e8800View commit details
Commits on Nov 26, 2022
-
Time out workflows after 45 minutes
GitHub's default timeout is 6 hours. Recently some of my GitHub Actions jobs have started randomly stalling for that long, which is inconvenient because it ties up a chunk of my runner quota. It apepars to be very rare for a job to recover after stalling. It's better to time out quicker and retry on a different runner.
Configuration menu - View commit details
-
Copy full SHA for 0bac51f - Browse repository at this point
Copy the full SHA 0bac51fView commit details
Commits on Dec 15, 2022
-
Configuration menu - View commit details
-
Copy full SHA for acecd9b - Browse repository at this point
Copy the full SHA acecd9bView commit details -
Disable backtrace CI on Rust 1.50
The `object` crate doesn't currently work on it. $ cargo +1.50.0 check --features backtrace warning: unused manifest key: package.rust-version error: failed to parse manifest at `/home/david/.cargo/registry/src/jackfan.us.kg-1ecc6299db9ec823/object-0.30.0/Cargo.toml` Caused by: feature `resolver` is required this Cargo does not support nightly features, but if you switch to nightly channel you can add `cargo-features = ["resolver"]` to enable this feature
Configuration menu - View commit details
-
Copy full SHA for 0f922d7 - Browse repository at this point
Copy the full SHA 0f922d7View commit details
Commits on Dec 16, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 613b261 - Browse repository at this point
Copy the full SHA 613b261View commit details
Commits on Dec 17, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 1cc707b - Browse repository at this point
Copy the full SHA 1cc707bView commit details
Commits on Dec 18, 2022
-
Opt out -Zrustdoc-scrape-examples on docs.rs
I'd like a chance to audit all the code that rustdoc is inserting into the docs. Currently I am skeptical that showing anyhow's internal usages of APIs is a net benefit to the public documentation. I am also skeptical that quite so many examples are needed, and that they should be featured so prominently in comparison to handwritten docs. Lastly I wish there were a way to turn this behavior off on a more granular basis.
Configuration menu - View commit details
-
Copy full SHA for c0a87d0 - Browse repository at this point
Copy the full SHA c0a87d0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 867763b - Browse repository at this point
Copy the full SHA 867763bView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 1.0.66...1.0.68