#global #singleton #piston

current

A library for setting current values for stack scope, such as application structure

8 releases

Uses old Rust 2015

0.1.2 Sep 6, 2016
0.1.1 Jun 24, 2015
0.0.10 Apr 4, 2015
0.0.7 Feb 21, 2015
0.0.5 Jan 21, 2015

#1453 in Rust patterns

Download history 42/week @ 2023-11-20 24/week @ 2023-11-27 10/week @ 2023-12-04 21/week @ 2023-12-11 30/week @ 2023-12-18 22/week @ 2023-12-25 4/week @ 2024-01-01 31/week @ 2024-01-08 25/week @ 2024-01-15 16/week @ 2024-01-22 9/week @ 2024-01-29 15/week @ 2024-02-05 30/week @ 2024-02-12 46/week @ 2024-02-19 56/week @ 2024-02-26 39/week @ 2024-03-04

173 downloads per month
Used in 6 crates (4 directly)

MIT license

6KB
96 lines

current Build Status

A library for setting current values for stack scope, such as application structure

Example project: Sea Birds' Breakfast

How to use it

See Best coding practices with current objects

This also posts safety guidelines for the library.

Motivation

In game programming, there are many kinds of "current" values:

  • The current window
  • The current device
  • The current sound driver
  • The current player object

There are two ways to use this library:

  • An unsafe version that ease refactoring between current objects and mutable references
  • A safe version that can be used in experimental library design

By setting these up as "current" values, you don't have to pass them around to each method. For example, you can write code like this (demonstrating the unsafe version):

e.press(|button| {
    let gun = unsafe { &mut *current_gun() };
    let player = unsafe { &mut *current_player() };
    if button == SHOOT {
        gun.shoot(player.aim);
    }
});

How to contribute

No runtime deps

Features