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 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258
// // DO NOT EDIT. THIS FILE IS GENERATED FROM ../../../dist/idl/xpctest_returncode.idl // /// `interface nsIXPCTestReturnCodeParent : nsISupports` /// // The actual type definition for the interface. This struct has methods // declared on it which will call through its vtable. You never want to pass // this type around by value, always pass it behind a reference. #[repr(C)] pub struct nsIXPCTestReturnCodeParent { vtable: *const nsIXPCTestReturnCodeParentVTable, /// This field is a phantomdata to ensure that the VTable type and any /// struct containing it is not safe to send across threads, as XPCOM is /// generally not threadsafe. /// /// XPCOM interfaces in general are not safe to send across threads. __nosync: ::std::marker::PhantomData<::std::rc::Rc<u8>>, } // Implementing XpCom for an interface exposes its IID, which allows for easy // use of the `.query_interface<T>` helper method. This also defines that // method for nsIXPCTestReturnCodeParent. unsafe impl XpCom for nsIXPCTestReturnCodeParent { const IID: nsIID = nsID(0x479e4532, 0x95cf, 0x48b8, [0xa9, 0x9b, 0x8a, 0x58, 0x81, 0xe4, 0x71, 0x38]); } // We need to implement the RefCounted trait so we can be used with `RefPtr`. // This trait teaches `RefPtr` how to manage our memory. unsafe impl RefCounted for nsIXPCTestReturnCodeParent { #[inline] unsafe fn addref(&self) { self.AddRef(); } #[inline] unsafe fn release(&self) { self.Release(); } } // This trait is implemented on all types which can be coerced to from nsIXPCTestReturnCodeParent. // It is used in the implementation of `fn coerce<T>`. We hide it from the // documentation, because it clutters it up a lot. #[doc(hidden)] pub trait nsIXPCTestReturnCodeParentCoerce { /// Cheaply cast a value of this type from a `nsIXPCTestReturnCodeParent`. fn coerce_from(v: &nsIXPCTestReturnCodeParent) -> &Self; } // The trivial implementation: We can obviously coerce ourselves to ourselves. impl nsIXPCTestReturnCodeParentCoerce for nsIXPCTestReturnCodeParent { #[inline] fn coerce_from(v: &nsIXPCTestReturnCodeParent) -> &Self { v } } impl nsIXPCTestReturnCodeParent { /// Cast this `nsIXPCTestReturnCodeParent` to one of its base interfaces. #[inline] pub fn coerce<T: nsIXPCTestReturnCodeParentCoerce>(&self) -> &T { T::coerce_from(self) } } // Every interface struct type implements `Deref` to its base interface. This // causes methods on the base interfaces to be directly avaliable on the // object. For example, you can call `.AddRef` or `.QueryInterface` directly // on any interface which inherits from `nsISupports`. impl ::std::ops::Deref for nsIXPCTestReturnCodeParent { type Target = nsISupports; #[inline] fn deref(&self) -> &nsISupports { unsafe { ::std::mem::transmute(self) } } } // Ensure we can use .coerce() to cast to our base types as well. Any type which // our base interface can coerce from should be coercable from us as well. impl<T: nsISupportsCoerce> nsIXPCTestReturnCodeParentCoerce for T { #[inline] fn coerce_from(v: &nsIXPCTestReturnCodeParent) -> &Self { T::coerce_from(v) } } // This struct represents the interface's VTable. A pointer to a statically // allocated version of this struct is at the beginning of every nsIXPCTestReturnCodeParent // object. It contains one pointer field for each method in the interface. In // the case where we can't generate a binding for a method, we include a void // pointer. #[doc(hidden)] #[repr(C)] pub struct nsIXPCTestReturnCodeParentVTable { /// We need to include the members from the base interface's vtable at the start /// of the VTable definition. pub __base: nsISupportsVTable, /* nsresult callChild (in long childBehavior); */ pub CallChild: unsafe extern "system" fn (this: *const nsIXPCTestReturnCodeParent, childBehavior: libc::int32_t, _retval: *mut nsresult) -> nsresult, } // The implementations of the function wrappers which are exposed to rust code. // Call these methods rather than manually calling through the VTable struct. impl nsIXPCTestReturnCodeParent { /// `nsresult callChild (in long childBehavior);` #[inline] pub unsafe fn CallChild(&self, childBehavior: libc::int32_t, _retval: *mut nsresult) -> nsresult { ((*self.vtable).CallChild)(self, childBehavior, _retval) } } /// `interface nsIXPCTestReturnCodeChild : nsISupports` /// // The actual type definition for the interface. This struct has methods // declared on it which will call through its vtable. You never want to pass // this type around by value, always pass it behind a reference. #[repr(C)] pub struct nsIXPCTestReturnCodeChild { vtable: *const nsIXPCTestReturnCodeChildVTable, /// This field is a phantomdata to ensure that the VTable type and any /// struct containing it is not safe to send across threads, as XPCOM is /// generally not threadsafe. /// /// XPCOM interfaces in general are not safe to send across threads. __nosync: ::std::marker::PhantomData<::std::rc::Rc<u8>>, } // Implementing XpCom for an interface exposes its IID, which allows for easy // use of the `.query_interface<T>` helper method. This also defines that // method for nsIXPCTestReturnCodeChild. unsafe impl XpCom for nsIXPCTestReturnCodeChild { const IID: nsIID = nsID(0x672cfd34, 0x1fd1, 0x455d, [0x99, 0x01, 0xd8, 0x79, 0xfa, 0x6f, 0xdb, 0x95]); } // We need to implement the RefCounted trait so we can be used with `RefPtr`. // This trait teaches `RefPtr` how to manage our memory. unsafe impl RefCounted for nsIXPCTestReturnCodeChild { #[inline] unsafe fn addref(&self) { self.AddRef(); } #[inline] unsafe fn release(&self) { self.Release(); } } // This trait is implemented on all types which can be coerced to from nsIXPCTestReturnCodeChild. // It is used in the implementation of `fn coerce<T>`. We hide it from the // documentation, because it clutters it up a lot. #[doc(hidden)] pub trait nsIXPCTestReturnCodeChildCoerce { /// Cheaply cast a value of this type from a `nsIXPCTestReturnCodeChild`. fn coerce_from(v: &nsIXPCTestReturnCodeChild) -> &Self; } // The trivial implementation: We can obviously coerce ourselves to ourselves. impl nsIXPCTestReturnCodeChildCoerce for nsIXPCTestReturnCodeChild { #[inline] fn coerce_from(v: &nsIXPCTestReturnCodeChild) -> &Self { v } } impl nsIXPCTestReturnCodeChild { /// Cast this `nsIXPCTestReturnCodeChild` to one of its base interfaces. #[inline] pub fn coerce<T: nsIXPCTestReturnCodeChildCoerce>(&self) -> &T { T::coerce_from(self) } } // Every interface struct type implements `Deref` to its base interface. This // causes methods on the base interfaces to be directly avaliable on the // object. For example, you can call `.AddRef` or `.QueryInterface` directly // on any interface which inherits from `nsISupports`. impl ::std::ops::Deref for nsIXPCTestReturnCodeChild { type Target = nsISupports; #[inline] fn deref(&self) -> &nsISupports { unsafe { ::std::mem::transmute(self) } } } // Ensure we can use .coerce() to cast to our base types as well. Any type which // our base interface can coerce from should be coercable from us as well. impl<T: nsISupportsCoerce> nsIXPCTestReturnCodeChildCoerce for T { #[inline] fn coerce_from(v: &nsIXPCTestReturnCodeChild) -> &Self { T::coerce_from(v) } } // This struct represents the interface's VTable. A pointer to a statically // allocated version of this struct is at the beginning of every nsIXPCTestReturnCodeChild // object. It contains one pointer field for each method in the interface. In // the case where we can't generate a binding for a method, we include a void // pointer. #[doc(hidden)] #[repr(C)] pub struct nsIXPCTestReturnCodeChildVTable { /// We need to include the members from the base interface's vtable at the start /// of the VTable definition. pub __base: nsISupportsVTable, /* void doIt (in long behavior); */ pub DoIt: unsafe extern "system" fn (this: *const nsIXPCTestReturnCodeChild, behavior: libc::int32_t) -> nsresult, } // The implementations of the function wrappers which are exposed to rust code. // Call these methods rather than manually calling through the VTable struct. impl nsIXPCTestReturnCodeChild { pub const CHILD_SHOULD_THROW: i64 = 0; pub const CHILD_SHOULD_RETURN_SUCCESS: i64 = 1; pub const CHILD_SHOULD_RETURN_RESULTCODE: i64 = 2; pub const CHILD_SHOULD_NEST_RESULTCODES: i64 = 3; /// `void doIt (in long behavior);` #[inline] pub unsafe fn DoIt(&self, behavior: libc::int32_t) -> nsresult { ((*self.vtable).DoIt)(self, behavior) } }