1 unstable release

Uses old Rust 2015

0.1.0 Nov 1, 2018

#33 in #singleton

Download history 59/week @ 2024-07-22 63/week @ 2024-07-29 59/week @ 2024-08-05 100/week @ 2024-08-12 44/week @ 2024-08-19 44/week @ 2024-08-26 53/week @ 2024-09-02 42/week @ 2024-09-09 46/week @ 2024-09-16 81/week @ 2024-09-23 53/week @ 2024-09-30 39/week @ 2024-10-14 45/week @ 2024-10-21 53/week @ 2024-10-28 47/week @ 2024-11-04

184 downloads per month
Used in 6 crates (via alloc-singleton)

MIT/Apache

8KB

owned-singleton

Owned singletons

License

Licensed under either of

at your option.

Contribution

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


lib.rs:

Owned singletons

An owned singleton is a proxy (struct) that grants exclusive access to a static mut variable.

Features

Owned singletons are smaller than &'static mut references; they are zero sized types.

Doesn't sound useful enough to you? The Singleton abstraction can be used to implement statically allocated memory pools whose handles are a single byte in size and are automatically deallocated on drop.

Examples

The Singleton attribute creates a proxy (struct) for the given static mut variable and implements the Singleton, Deref, DerefMut and StableDerefs traits for it.

use owned_singleton::Singleton;

#[Singleton]
static mut FOO: u32 = 0;

let mut foo = unsafe { FOO::new() };
assert_eq!(*foo, 0);
*foo += 1;
assert_eq!(*foo, 1);

let bar: &'static mut u32 = foo.unwrap();
assert_eq!(*bar, 1);

The Singleton attribute doesn't implement the Send or Sync traits by default; this results in a proxy struct that does not implement Send or Sync. To opt into the Send and Sync traits add the Send and Sync arguments to the Singleton attribute.

use owned_singleton::Singleton;

#[Singleton(Send, Sync)]
static mut FOO: u32 = 0;

fn is_send<T>() where T: Send {}
fn is_sync<T>() where T: Sync {}

is_send::<FOO>();
is_sync::<FOO>();

Using Singleton on a static variable results in DerefMut not being implemented for the proxy struct. However, the proxy struct will still be a handle to a static mut variable so there's no Sync requirement on the type of the static mut variable.

use std::marker::PhantomData;

use owned_singleton::Singleton;

// `PhantomData<*const ()>` does not implement `Send` or `Sync`
#[Singleton]
static FOO: PhantomData<*const ()> = PhantomData;

Dependencies

~2.5MB
~54K SLoC