bindgen 0.29.0

Automatically generates Rust FFI bindings to C and C++ libraries.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97

//! Traits for determining whether we can derive traits for a thing or not.

use super::context::BindgenContext;

/// A trait that encapsulates the logic for whether or not we can derive `Debug`
/// for a given thing.
///
/// This should ideally be a no-op that just returns `true`, but instead needs
/// to be a recursive method that checks whether all the proper members can
/// derive debug or not, because of the limit rust has on 32 items as max in the
/// array.
pub trait CanDeriveDebug {
    /// Return `true` if `Debug` can be derived for this thing, `false`
    /// otherwise.
    fn can_derive_debug(&self, ctx: &BindgenContext) -> bool;
}

/// A trait that encapsulates the logic for whether or not we can derive `Debug`.
/// The difference between this trait and the CanDeriveDebug is that the type
/// implementing this trait cannot use recursion or lookup result from fix point
/// analysis. It's a helper trait for fix point analysis.
pub trait CanTriviallyDeriveDebug {

    /// Serve the same purpose as the Extra in CanDeriveDebug.
    type Extra;

    /// Return `true` if `Debug` can be derived for this thing, `false`
    /// otherwise.
    fn can_trivially_derive_debug(&self,
                        ctx: &BindgenContext,
                        extra: Self::Extra)
                        -> bool;
}

/// A trait that encapsulates the logic for whether or not we can derive `Copy`
/// for a given thing.
pub trait CanDeriveCopy<'a> {
    /// Implementations can define this type to get access to any extra
    /// information required to determine whether they can derive `Copy`. If
    /// extra information is unneeded, then this should simply be the unit type.
    type Extra;

    /// Return `true` if `Copy` can be derived for this thing, `false`
    /// otherwise.
    fn can_derive_copy(&'a self,
                       ctx: &'a BindgenContext,
                       extra: Self::Extra)
                       -> bool;

    /// For some reason, deriving copies of an array of a type that is not known
    /// to be `Copy` is a compile error. e.g.:
    ///
    /// ```rust
    /// #[derive(Copy, Clone)]
    /// struct A<T> {
    ///     member: T,
    /// }
    /// ```
    ///
    /// is fine, while:
    ///
    /// ```rust,ignore
    /// #[derive(Copy, Clone)]
    /// struct A<T> {
    ///     member: [T; 1],
    /// }
    /// ```
    ///
    /// is an error.
    ///
    /// That's the whole point of the existence of `can_derive_copy_in_array`.
    fn can_derive_copy_in_array(&'a self,
                                ctx: &'a BindgenContext,
                                extra: Self::Extra)
                                -> bool;
}

/// A trait that encapsulates the logic for whether or not we can derive `Default`
/// for a given thing.
///
/// This should ideally be a no-op that just returns `true`, but instead needs
/// to be a recursive method that checks whether all the proper members can
/// derive default or not, because of the limit rust has on 32 items as max in the
/// array.
pub trait CanDeriveDefault<'a> {
    /// Implementations can define this type to get access to any extra
    /// information required to determine whether they can derive `Default`. If
    /// extra information is unneeded, then this should simply be the unit type.
    type Extra;

    /// Return `true` if `Default` can be derived for this thing, `false`
    /// otherwise.
    fn can_derive_default(&self,
                          ctx: &BindgenContext,
                          extra: Self::Extra)
                          -> bool;
}