#types #send #type #utility #emulate #who #different

relevant

A small utility type to emulate must-use types

7 unstable releases (3 breaking)

0.4.2 May 23, 2019
0.4.1 Apr 1, 2019
0.4.0 Jan 22, 2019
0.3.0 Dec 1, 2018
0.1.1 Jan 26, 2018
Download history 176/week @ 2019-03-30 400/week @ 2019-04-06 183/week @ 2019-04-13 120/week @ 2019-04-20 85/week @ 2019-04-27 154/week @ 2019-05-04 96/week @ 2019-05-11 573/week @ 2019-05-18 670/week @ 2019-05-25 777/week @ 2019-06-01 1001/week @ 2019-06-08 1057/week @ 2019-06-15 945/week @ 2019-06-22 912/week @ 2019-06-29 806/week @ 2019-07-06

1,072 downloads per month
Used in 26 crates (9 directly)

MIT/Apache

7KB
60 lines

Relevant

A small utility type to emulate must-use types. They are different from #[must_use] attribute in that the one who have an instance must either send it somewhere else or dispose it manually.

This must be desired for types that need manual destruction which can't be implemented with Drop trait. For example resource handler created from some source and that must be returned to the same source.

Usage

The type Relevant is non-droppable. As limitation of current implementation it panics when dropped. To make type non-droppable it must contain non-droppable type (Relevant type for example).

Example


struct SourceOfFoos {
    handle: u64,
}

/// Foo must be destroyed manually.
struct Foo {
   handle: u64,
   relevant: Relevant,
}

/// Function from C library to create `Foo`
/// Access to same source must be synchronized.
extern "C" create_foo(source: u64) -> u64;

/// Function from C library to destroy `Foo`.
/// Access to same source must be synchronized.
extern "C" destroy_foo(source: u64, foo: u64) -> u64;

impl SourceOfFoos {
    fn create_foo(&mut self) -> Foo {
        Foo {
            handle: create_foo(self.handle),
            relevant: Relevant,
        }
    }

    fn destroy_foo(&mut self, foo: Foo) {
        destroy_foo(self.handle, foo.handle);
        foo.relevant.dispose();
    }
}

Now it is not possible to accidentally drop Foo and leak handle. Of course it always possible to explicitly std::mem::forget relevant type. But it will be deliberate leak.

Dependencies

~226KB