Copy as Markdown
Other Tools
//
// DO NOT EDIT. THIS FILE IS GENERATED FROM $SRCDIR/widget/android/tests/nsIOhttpClientTest.idl
//
/// `interface ohttpClientTestCallback : 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 ohttpClientTestCallback {
vtable: &'static ohttpClientTestCallbackVTable,
/// This field is a phantomdata to ensure that the VTable type and any
/// struct containing it is not safe to send across threads by default, as
/// XPCOM is generally not threadsafe.
///
/// If this type is marked as [rust_sync], there will be explicit `Send` and
/// `Sync` implementations on this type, which will override the inherited
/// negative impls from `Rc`.
__nosync: ::std::marker::PhantomData<::std::rc::Rc<u8>>,
// Make the rust compiler aware that there might be interior mutability
// in what actually implements the interface. This works around UB
// introduced by https://github.com/llvm/llvm-project/commit/01859da84bad95fd51d6a03b08b60c660e642a4f
// that a rust lint would make blatantly obvious, but doesn't exist.
// This prevents optimizations, but those optimizations weren't available
// before rustc switched to LLVM 16, and they now cause problems because
// of the UB.
// Until there's a lint available to find all our UB, it's simpler to
// avoid the UB in the first place, at the cost of preventing optimizations
// in places that don't cause UB. But again, those optimizations weren't
// available before.
__maybe_interior_mutability: ::std::cell::UnsafeCell<[u8; 0]>,
}
// 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 ohttpClientTestCallback.
unsafe impl XpCom for ohttpClientTestCallback {
const IID: nsIID = nsID(0xcdec8db3, 0x3868, 0x41e7,
[0xa9, 0x1a, 0x68, 0xa3, 0xb5, 0xa2, 0x4d, 0xe0]);
}
// 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 ohttpClientTestCallback {
#[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 ohttpClientTestCallback.
// 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 ohttpClientTestCallbackCoerce {
/// Cheaply cast a value of this type from a `ohttpClientTestCallback`.
fn coerce_from(v: &ohttpClientTestCallback) -> &Self;
}
// The trivial implementation: We can obviously coerce ourselves to ourselves.
impl ohttpClientTestCallbackCoerce for ohttpClientTestCallback {
#[inline]
fn coerce_from(v: &ohttpClientTestCallback) -> &Self {
v
}
}
impl ohttpClientTestCallback {
/// Cast this `ohttpClientTestCallback` to one of its base interfaces.
#[inline]
pub fn coerce<T: ohttpClientTestCallbackCoerce>(&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 ohttpClientTestCallback {
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> ohttpClientTestCallbackCoerce for T {
#[inline]
fn coerce_from(v: &ohttpClientTestCallback) -> &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 ohttpClientTestCallback
// 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 ohttpClientTestCallbackVTable {
/// We need to include the members from the base interface's vtable at the start
/// of the VTable definition.
pub __base: nsISupportsVTable,
/* void onResponse (in ACString url, in long statusCode, in Array<ACString> headerKeys, in Array<ACString> headerValues, in ACString errorMessage); */
pub OnResponse: unsafe extern "system" fn (this: *const ohttpClientTestCallback, url: *const ::nsstring::nsACString, statusCode: i32, headerKeys: *const thin_vec::ThinVec<::nsstring::nsCString>, headerValues: *const thin_vec::ThinVec<::nsstring::nsCString>, errorMessage: *const ::nsstring::nsACString) -> ::nserror::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 ohttpClientTestCallback {
/// `void onResponse (in ACString url, in long statusCode, in Array<ACString> headerKeys, in Array<ACString> headerValues, in ACString errorMessage);`
#[inline]
pub unsafe fn OnResponse(&self, url: *const ::nsstring::nsACString, statusCode: i32, headerKeys: *const thin_vec::ThinVec<::nsstring::nsCString>, headerValues: *const thin_vec::ThinVec<::nsstring::nsCString>, errorMessage: *const ::nsstring::nsACString) -> ::nserror::nsresult {
((*self.vtable).OnResponse)(self, url, statusCode, headerKeys, headerValues, errorMessage)
}
}
/// `interface nsIOhttpClientTest : 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 nsIOhttpClientTest {
vtable: &'static nsIOhttpClientTestVTable,
/// This field is a phantomdata to ensure that the VTable type and any
/// struct containing it is not safe to send across threads by default, as
/// XPCOM is generally not threadsafe.
///
/// If this type is marked as [rust_sync], there will be explicit `Send` and
/// `Sync` implementations on this type, which will override the inherited
/// negative impls from `Rc`.
__nosync: ::std::marker::PhantomData<::std::rc::Rc<u8>>,
// Make the rust compiler aware that there might be interior mutability
// in what actually implements the interface. This works around UB
// introduced by https://github.com/llvm/llvm-project/commit/01859da84bad95fd51d6a03b08b60c660e642a4f
// that a rust lint would make blatantly obvious, but doesn't exist.
// This prevents optimizations, but those optimizations weren't available
// before rustc switched to LLVM 16, and they now cause problems because
// of the UB.
// Until there's a lint available to find all our UB, it's simpler to
// avoid the UB in the first place, at the cost of preventing optimizations
// in places that don't cause UB. But again, those optimizations weren't
// available before.
__maybe_interior_mutability: ::std::cell::UnsafeCell<[u8; 0]>,
}
// 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 nsIOhttpClientTest.
unsafe impl XpCom for nsIOhttpClientTest {
const IID: nsIID = nsID(0xb3150bd2, 0x689c, 0x4cf0,
[0xb4, 0xee, 0x4f, 0x90, 0xaa, 0xf1, 0xcb, 0xd3]);
}
// 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 nsIOhttpClientTest {
#[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 nsIOhttpClientTest.
// 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 nsIOhttpClientTestCoerce {
/// Cheaply cast a value of this type from a `nsIOhttpClientTest`.
fn coerce_from(v: &nsIOhttpClientTest) -> &Self;
}
// The trivial implementation: We can obviously coerce ourselves to ourselves.
impl nsIOhttpClientTestCoerce for nsIOhttpClientTest {
#[inline]
fn coerce_from(v: &nsIOhttpClientTest) -> &Self {
v
}
}
impl nsIOhttpClientTest {
/// Cast this `nsIOhttpClientTest` to one of its base interfaces.
#[inline]
pub fn coerce<T: nsIOhttpClientTestCoerce>(&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 nsIOhttpClientTest {
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> nsIOhttpClientTestCoerce for T {
#[inline]
fn coerce_from(v: &nsIOhttpClientTest) -> &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 nsIOhttpClientTest
// 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 nsIOhttpClientTestVTable {
/// We need to include the members from the base interface's vtable at the start
/// of the VTable definition.
pub __base: nsISupportsVTable,
/* void fetch (in ACString url, in ACString method, in ACString body, in Array<ACString> headerKeys, in Array<ACString> headerValues, in ohttpClientTestCallback callback); */
pub Fetch: unsafe extern "system" fn (this: *const nsIOhttpClientTest, url: *const ::nsstring::nsACString, method: *const ::nsstring::nsACString, body: *const ::nsstring::nsACString, headerKeys: *const thin_vec::ThinVec<::nsstring::nsCString>, headerValues: *const thin_vec::ThinVec<::nsstring::nsCString>, callback: *const ohttpClientTestCallback) -> ::nserror::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 nsIOhttpClientTest {
/// `void fetch (in ACString url, in ACString method, in ACString body, in Array<ACString> headerKeys, in Array<ACString> headerValues, in ohttpClientTestCallback callback);`
#[inline]
pub unsafe fn Fetch(&self, url: *const ::nsstring::nsACString, method: *const ::nsstring::nsACString, body: *const ::nsstring::nsACString, headerKeys: *const thin_vec::ThinVec<::nsstring::nsCString>, headerValues: *const thin_vec::ThinVec<::nsstring::nsCString>, callback: *const ohttpClientTestCallback) -> ::nserror::nsresult {
((*self.vtable).Fetch)(self, url, method, body, headerKeys, headerValues, callback)
}
}