libc-print 0.3.0

println! and eprintln! macros on libc without stdlib
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52

# no_std libc print/println/eprint/eprintln/dbg

![Build Status](https://github.com/mmastrac/rust-libc-print/actions/workflows/rust.yml/badge.svg)
[![docs.rs](https://docs.rs/libc-print/badge.svg)](https://docs.rs/libc-print)
[![crates.io](https://img.shields.io/crates/v/libc-print.svg)](https://crates.io/crates/libc-print)

Implements `println!`, `eprintln!` and `dbg!` on the `libc` crate without 
requiring the use of an allocator.

Allows you to use these macros in a `#![no_std]` context, or in a 
situation where the traditional Rust streams might not be available 
(ie: at process shutdown time).

By default this crate provides `libc_`-prefixed macros, but also allows consumers to
import macros with the same name as the stdlib printing macros via the `std_name`
module.

## Platform Support

For platforms with `write` in libc, this crate uses `libc::write`. For `unknown`
and `none` OS targets, the user is required to provide a `write` function via
the linker.

This crate support `miri` on all platforms, though it may choose different code
paths for compatibility reasons.

## Usage

Exactly as you'd use `println!`, `eprintln!` and `dbg!`.

```rust
#![no_std]

// Use the default `libc_`-prefixed macros:
libc_println!("Hello {}!", "stdout");
libc_eprintln!("Hello {}!", "stderr");
let a = 2;
let b = libc_dbg!(a * 2) + 1;
assert_eq!(b, 5);
```

Or you can import aliases to `std` names:

```rust
use libc_print::std_name::{println, eprintln, dbg};

println!("Hello {}!", "stdout");
eprintln!("Hello {}!", "stderr");
let a = 2;
let b = dbg!(a * 2) + 1;
assert_eq!(b, 5);
```