autocfg
autocfg copied to clipboard
cuviper
Automatic cfg for Rust compiler features
Closes #41. There *is* a tradeoff here: this means that a probe can no longer test if something is denied by a lint rather than a hard error. However, I...
Alternative to #35, #42. cc #24, #28. This implements the callback based `with_features` approach mentioned in #35. I've written the test to just use `.probe("")` to avoid making the test...
Alternative to #35. cc #24, #28. This API puts the burden onto the user to know how to best check that a feature works as expected (whatever statements are used...
As mentioned in bluss/indexmap#144, the [`rust-server` openapi-generator](https://openapi-generator.tech/docs/generators/rust-server) generates a local `.cargo/config` with `-W missing_docs` and `-D warnings`. This causes ``` warning: autocfg could not probe for `std` error: missing documentation...
But add an environment variable to allow showing it, if wanted. Fixes #30
Second attempt at probing with features. First attempt was #33. This PR adds two methods to `AutoCfg`: `enable_feature()`, which enables a nightly feature to be used in probes, and `disable_feature()`,...
build.rs: ``` fn main() { assert!(autocfg::new().probe_sysroot_crate("std")); } ``` `cargo build` works fine for any target where libstd is already distributed. `cargo build --target x86_64-uwp-windows-msvc -Z build-std` panics even though the...
Hi, Firefox's build and CI tooling parses the logs including verbose build script output to find and highlight errors. It helps a lot with quickly figuring out where build problems...
Would it be a good idea to allow consumers of autocfg to probe if their compiler is nightly or not? This could be used in instances where a crate uses...
We already detected whether we should be using `#![no_std]` for targets without `std` (#5), but now you can get that result and even change it.
