itsscb/eyre
1
0
Fork 0
mirror of https://github.com/eyre-rs/eyre.git synced 2025-09-26 20:40:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

emit rustc-check-cfg info and fix doc_lazy_continuation clippy warning (#200)

Browse Source 
This should resolve clippy warnings on master
This commit is contained in:
Jane Losare-Lusby 2024-08-29 13:56:05 -07:00 committed by GitHub
parent fc83cb8125
commit 7706273bcf
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
4 changed files with 18 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
.gitignore vendored
View File

@ -1,3 +1,2 @@
/target
**/*.rs.bk
tags

3
color-spantrace/build.rs
View File

@ -20,6 +20,9 @@ enum Toolchain {
impl Toolchain {
fn set_feature(self) {
println!("cargo:rustc-check-cfg=cfg(nightly)");
println!("cargo:rustc-check-cfg=cfg(beta)");
println!("cargo:rustc-check-cfg=cfg(stable)");
match self {
Toolchain::Nightly => println!("cargo:rustc-cfg=nightly"),
Toolchain::Beta => println!("cargo:rustc-cfg=beta"),

7
eyre/build.rs
View File

@ -5,6 +5,13 @@ use std::{
};
fn main() {
println!("cargo:rustc-check-cfg=cfg(nightly)");
println!("cargo:rustc-check-cfg=cfg(track_caller)");
println!("cargo:rustc-check-cfg=cfg(generic_member_access)");
println!("cargo:rustc-check-cfg=cfg(eyre_no_fmt_args_capture)");
println!("cargo:rustc-check-cfg=cfg(backtrace)");
println!("cargo:rustc-check-cfg=cfg(eyre_no_fmt_arguments_as_str)");
println!("cargo:rustc-check-cfg=cfg(doc_cfg)");
let ac = autocfg::new();
// https://github.com/rust-lang/rust/issues/99301 [nightly]

16
eyre/src/lib.rs
View File

@ -39,16 +39,16 @@
//! to avoid using `eyre::Report` as your public error type.
//!
//! - You export an undocumented error interface that is otherwise still
//! accessible via downcast, making it hard for users to react to specific
//! errors while not preventing them from depending on details you didn't mean
//! to make part of your public API.
//! accessible via downcast, making it hard for users to react to specific
//! errors while not preventing them from depending on details you didn't mean
//! to make part of your public API.
//! - This in turn makes the error types of all libraries you use a part of
//! your public API as well, and makes changing any of those libraries into
//! undetectable runtime breakage.
//! your public API as well, and makes changing any of those libraries into
//! undetectable runtime breakage.
//! - If many of your errors are constructed from strings, you encourage your
//! users to use string comparison for reacting to specific errors, which is
//! brittle and turns updating error messages into potentially undetectable
//! runtime breakage.
//! users to use string comparison for reacting to specific errors, which is
//! brittle and turns updating error messages into potentially undetectable
//! runtime breakage.
//!
//! ## Details
//!