#plugin #types

plugin

Lazily evaluated, order-independent plugins for extensible types

11 releases

0.2.6 Apr 22, 2015
0.2.5 Apr 3, 2015
0.2.4 Mar 31, 2015
0.2.2 Feb 28, 2015
0.0.0 Nov 11, 2014

#3 in Multimedia

Download history 2168/week @ 2018-08-21 2234/week @ 2018-08-28 2583/week @ 2018-09-04 2445/week @ 2018-09-11 2344/week @ 2018-09-18 2371/week @ 2018-09-25 2458/week @ 2018-10-02 3012/week @ 2018-10-09 2565/week @ 2018-10-16 2924/week @ 2018-10-23 2786/week @ 2018-10-30 2674/week @ 2018-11-06 2214/week @ 2018-11-13

12,815 downloads per month
Used in 156 crates (18 directly)

MIT license

8KB
113 lines

Plugin

Type-Safe, Lazily Evaluated, Plugins for Extensible Types

Plugins provide a consistent interface for mixin methods. You can use a plugin anywhere you would use a "mixin" trait and an implementation.

Example Usage

// Define a struct.
struct IntPlugin;

// Map it onto an `i32` value.
impl Assoc<i32> for IntPlugin {}

// Define the plugin evaluation function.
// `Extended` is a type that implements `Extensible`.
impl PluginFor<Extended, i32> for IntPlugin {
    fn eval(_: &Extended, _: Phantom<IntPlugin>) -> Option<i32> {
        Some(0i32)
    }
}
assert_eq!(extended.get::<IntPlugin>().unwrap(), 0i32);

To do the same thing with a trait, one could do:

trait IntProducer {
    fn get_int_value(&self) -> Option<i32>;
}

impl IntProducer for Extended {
    fn get_int_value(&self) -> Option<i32> {
        Some(0i32)
    }
}

Although using a raw trait is less code, plugins provide the following advantages:

  • Automatic caching of values. Calling a method again is a constant time operation! This is particularly useful in pipeline structures where only the extensible object is passed around.
  • A consistent interface, which also allows for neater name clash resolution. Two modules that provide PluginX can be differentiated using a module prefix.
e.get::<mod1::PluginX>();
e.get::<mod2::PluginX>();

Dependencies

~29KB