Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.
bspeice 963d634923
Merge pull request #9 from bspeice/deprecation
il y a 2 ans
examples Renaming and a new macro il y a 2 ans
qadapt-macro Mark everything deprecated il y a 2 ans
src Mark everything deprecated il y a 2 ans
tests Add a release-only test for `is_active()` behavior il y a 2 ans
.gitignore Add an `is_active` function, and remove panic on not using il y a 2 ans
.travis.yml Remove qadapt-spin from the publish build il y a 2 ans
CHANGELOG.md Mark everything deprecated il y a 2 ans
CONTRIBUTING.md Use new CI template il y a 2 ans
CONTRIBUTORS.md Use new CI template il y a 2 ans
Cargo.toml Go back to the `spin` crate as a dependency il y a 2 ans
LICENSE Use new CI template il y a 2 ans
Makefile Prepare for 1.0 il y a 2 ans
README.md Mark everything deprecated il y a 2 ans
appveyor.yml Add testing in stable/beta branches il y a 2 ans
rustfmt.toml Use new CI template il y a 2 ans

README.md

qadapt

crates.io docs.rs codecov travisci appveyor


debug_assert! for your memory usage

Please note: This crate has been deprecated in favor of alloc-counter.

This allocator is a helper for writing high-performance code that is memory-sensitive; a thread panic will be triggered if a function annotated with #[no_alloc], or code inside an assert_no_alloc! macro interacts with the allocator in any way. Wanton allocations and unforeseen drops no more - this library lets you focus on writing code without worrying if Rust properly managed to inline the variable into the stack.

Now, an allocator blowing up in production is a scary thought; that's why QADAPT is designed to strip its own code out whenever you're running with a release build. Just like the debug_assert! macro in Rust's standard library, it's safe to use without worrying about a unforeseen circumstance causing your application to crash.

Usage

Actually making use of QADAPT is straight-forward. To set up the allocator, place the following snippet in either your program binaries (main.rs) or tests:

use qadapt::QADAPT;

#[global_allocator]
static Q: QADAPT = QADAPT;

fn main() {
    # // Because `debug_assertions` are on for doctests in release mode
    # // we have to add an extra guard.
    # if qadapt::is_active() {
    assert!(qadapt::is_active());
    # }
}

After that, there are two ways of telling QADAPT that it should trigger a panic:

  1. Annotate functions with the #[no_alloc] proc macro:
use qadapt::no_alloc;
use qadapt::QADAPT;
use std::panic::catch_unwind;

#[global_allocator]
static Q: QADAPT = QADAPT;

// This function is fine, there are no allocations here
#[no_alloc]
fn do_math() -> u8 {
    2 + 2
}

// This function will trigger a panic when called
#[no_alloc]
fn does_panic() -> Box<u32> {
    Box::new(5)
}

fn main() {
    do_math();

    let err = catch_unwind(|| does_panic());
    # if qadapt::is_active() {
    assert!(err.is_err());
    # }
}
  1. Evaluate expressions with the assert_no_alloc! macro
use qadapt::assert_no_alloc;
use qadapt::QADAPT;

#[global_allocator]
static Q: QADAPT = QADAPT;

fn main() {
    // This code is allowed to trigger an allocation
    let b = Box::new(8);
    
    // This code would panic if an allocation occurred inside it
    let x = assert_no_alloc!(*b + 2);
    assert_eq!(x, 10);
}