#traits #expose #proc-macro #hidden #exposing

macro hidden-trait

Proc macro for exposing a trait implementation

3 releases

0.1.2 Dec 11, 2022
0.1.1 Dec 11, 2022
0.1.0 Dec 10, 2022

#9 in #exposing

Download history 1978/week @ 2024-11-16 2013/week @ 2024-11-23 2231/week @ 2024-11-30 2286/week @ 2024-12-07 2651/week @ 2024-12-14 1941/week @ 2024-12-21 2356/week @ 2024-12-28 4150/week @ 2025-01-04 3834/week @ 2025-01-11 2819/week @ 2025-01-18 2934/week @ 2025-01-25 3022/week @ 2025-02-01 2820/week @ 2025-02-08 2941/week @ 2025-02-15 3130/week @ 2025-02-22 2929/week @ 2025-03-01

12,368 downloads per month
Used in 7 crates (via blade-graphics)

MIT license

5KB
66 lines

hidden-trait

Build Status Docs Crates.io

This library is a proc macro to expose a trait implementation.

The case we are trying to solve here: a library exposes some concrete structure for people to use. There can be multiple of them (e.g. Vector2, Vector3, Vector4 in a math library), or maybe it's one per platform (Vulkan vs Metal). Important part is - internally the library would like to have a trait implemented by this public type, but it doesn't want to expose the trait itself because of ergonomic reasons. Hence, "hidden-trait" to rescue.

mod hidden {
    trait Foo {
        fn foo(&self) -> u32;
    }

    pub struct Bar;

    #[hidden_trait::expose]
    impl Foo for Bar {
        fn foo(&self) -> u32 {
            42
        }
    }
}

fn main() {
    let bar = hidden::Bar;
    // calling the trait method as if it's ours
    bar.foo();
}

Dependencies

~1.5MB
~39K SLoC