dirty_static 0.1.2

A container for an immutable value that allows sneaky reloading in debug mode (via UnsafeCell) while keeping the data safe and constant in release mode. This allows you to tweak data while testing an application, without having that data be mutable when the application is released. Intended for use with game assets, but suitable for any interactive application.
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

# dirty_static

[![Crates.io](https://img.shields.io/crates/v/dirty_static.svg)](https://crates.io/crates/dirty_static)
[![Docs.rs](https://docs.rs/dirty_static/badge.svg)](https://docs.rs/dirty_static/latest/dirty_static/)

This crate provides a container for a value, `DirtyStatic`, which
allows mutation in debug mode (via `UnsafeCell`), but not in
release mode.

This allows you to tweak data while testing an application,
without having that data be mutable when the application is
released.

There are also two features available:

1. `force-dynamic` which allows replacing the value of a
    `DirtyStatic` even in release mode.
2. `force-static` which disallows replacing the value of a
    `DirtyStatic` even in debug mode.

## Usage

```rust
// In debug mode
use dirty_static::DirtyStatic;

let c = DirtyStatic::new(100);
unsafe {
    c.replace(200);
}

assert_eq!(*c, 200);
```

```rust
// In release mode
use dirty_static::DirtyStatic;

let c = DirtyStatic::new(100);
unsafe {
    c.replace(200);
}

assert_eq!(*c, 100);
```