if_rust_version

KO | EN

gitlite — search

#javascript #python #hacktoberfest #react #ai #typescript #llm #go #golang #android #machine-learning #rust #deep-learning #linux

if_rust_version

★ 12 Open GitHub ↗

Macro to enable code depending on the rust version

Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# if_rust_version

[![Build Status](https://travis-ci.org/ogoffart/if_rust_version.svg?branch=master)](https://travis-ci.org/ogoffart/if_rust_version)
[![Crates.io](https://img.shields.io/crates/v/if_rust_version.svg)](https://crates.io/crates/if_rust_version)
[![docs](https://docs.rs/if_rust_version/badge.svg)](https://docs.rs/if_rust_version)
![Minimum Rust version: 1.12](https://img.shields.io/badge/rustc-1.12+-lightgray.svg)

This is a small crate that just export one macro that allow you to have code
conditionally of the rust version.
The `if_rust_version!` macro allows you to still
support older version
of rustc while still using conditionally new features of the compiler

## Examples

The release of rust 1.36 stabilized the `MaybeUninit` union as a replacement
for the to be deprecated `mem::uninitialized`. One might want to use
MaybeUninit when the compiler supports it, but not without requiring a recent compiler.

The `if_rust_version!` macro is exactly what one needs:

```rust
if_rust_version! { >= 1.36 {
    let mut x = std::mem::MaybeUninit::<u32>::uninit();
    unsafe { x.as_mut_ptr().write(32); }
    let xx = unsafe { x.assume_init() };
} else {
    let mut xx : u32 = unsafe { mem::uninitialized() };
    unsafe { ptr::write(&mut xx as *mut u32, 32); }
}}
```

The macro can be used to declare items or expression.

It can also be usefull to declare macro for pattern you often use.
For example, if we want to declare functions const from rust 1.31 which
introduced the concept:

```rust
if_rust_version! { >= 1.31 {
    // just a identity macro that forward the item
    macro_rules! const_fn { ($f:item) => { $f } }
} else {
    // remove the 'const'
    macro_rules! const_fn {
        ($(#[$m:meta])* const fn $($rest:tt)*) => { $(#[$m])* fn $($rest)* };
        ($(#[$m:meta])* pub const fn $($rest:tt)*) => {
            $(#[$m])*
            /// This function is a const fn from rust 1.31
            pub fn $($rest)*
        };
    }
}}

const_fn!{
    /// This function is const chen the compiler supports it
    pub const fn hello(x : u32) -> u32 { x + 2 }
}
```

## Minimum Rust version

The minimum rust version is rust 1.12, because previous versions were
not expanding `tt` correcrtly in `macro_rules!`

This crate has no dependencies, and is `#![no-std]`.

## Comparison with other crates

There are other crates that check the rust version number:

The main difference with
[version_check](https://crates.io/crates/version_check) and
[rustc_version](https://crates.io/crates/rustc_version) is that these crates
are meant to to be used by first writing a `build.rs` script to then add some
feature flag.

[rustversion](https://crates.io/crates/rustversion) is a attribute macro,
this has the disadvantage not to be able to be used for feature which add
new grammar to the language (example: `?` or `10u128` or `impl Trait`).
Also attribute macros were only stabilized recently, and do not support
expanding to expressions yet. Not to mention the need to use heavy dependencies
such as `syn` to develop procedural macro.

There is also a proposed [RFC 2523](https://github.com/rust-lang/rfcs/pull/2523)
which suggest allowing to query the rust version via the `#[cfg(...)]` attributes.

## Licenses:

MIT/Apache-2.0

if_rust_version

Download

Today's picks

Was this content helpful?

Recent Feedback

if_rust_version

Download

Today's picks

Was this content helpful?

Recent Feedback

Download README