match_cfg

Convenience macro for defining items depending on large number of #[cfg]s

Latest version: 0.1.0 registry icon
Maintenance score
0
Safety score
0
Popularity score
70
Check your open source dependency risks. Get immediate insight about security, stability and licensing risks.
Security
  Vulnerabilities
Version Suggest Low Medium High Critical
0.1.0 0 0 0 0 0

Stability
Latest release:

0.1.0 - This version may not be safe as it has not been updated for a long time. Find out if your coding project uses this component and get notified of any reported security vulnerabilities with Meterian-X Open Source Security Platform

Licensing

Maintain your licence declarations and avoid unwanted licences to protect your IP the way you intended.

Apache-2.0   -   Apache License 2.0

Not a wildcard

Not proprietary

OSI Compliant


MIT   -   MIT License

Not a wildcard

Not proprietary

OSI Compliant



match_cfg

Build Status

Documentation

Minimum Supported Rust Version: 1.13.0.

A convenience macro to ergonomically define an item depending on a large number of #[cfg] parameters. Structured like match statement, the first matching branch is the item that gets emitted.

[dependencies]
match_cfg = "0.1"

The use_core feature is enabled by default and builds the crate with libcore as a dependency by using the #![no_std] attribute. When this feature is disabled, this crate is built without libcore support by using the #![no_core] attribute - this makes use of the #![feature(no_core)] and requires a nightly version of Rust.

Example

#[macro_use(match_cfg)]
extern crate match_cfg;

match_cfg! {
    #[cfg(unix)] => {
         fn foo() { /* unix specific functionality */ }
     }
     #[cfg(target_pointer_width = "32")] => {
         fn foo() { /* non-unix, 32-bit functionality */ }
     }
     _ => {
         fn foo() { /* fallback implementation */ }
     }
}

fn main() {
    foo();
}

License

This project is licensed under either of

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in Serde by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.