Copy as Markdown
Other Tools
//
// DO NOT EDIT. THIS FILE IS GENERATED FROM $SRCDIR/security/sandbox/common/mozISandboxSettings.idl
//
/// `interface mozISandboxSettings : 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 mozISandboxSettings {
vtable: &'static mozISandboxSettingsVTable,
/// 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 mozISandboxSettings.
unsafe impl XpCom for mozISandboxSettings {
const IID: nsIID = nsID(0x5516303d, 0x9007, 0x45a0,
[0x94, 0xb9, 0x94, 0x0e, 0xf1, 0x34, 0xa6, 0xe2]);
}
// 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 mozISandboxSettings {
#[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 mozISandboxSettings.
// 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 mozISandboxSettingsCoerce {
/// Cheaply cast a value of this type from a `mozISandboxSettings`.
fn coerce_from(v: &mozISandboxSettings) -> &Self;
}
// The trivial implementation: We can obviously coerce ourselves to ourselves.
impl mozISandboxSettingsCoerce for mozISandboxSettings {
#[inline]
fn coerce_from(v: &mozISandboxSettings) -> &Self {
v
}
}
impl mozISandboxSettings {
/// Cast this `mozISandboxSettings` to one of its base interfaces.
#[inline]
pub fn coerce<T: mozISandboxSettingsCoerce>(&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 mozISandboxSettings {
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> mozISandboxSettingsCoerce for T {
#[inline]
fn coerce_from(v: &mozISandboxSettings) -> &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 mozISandboxSettings
// 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 mozISandboxSettingsVTable {
/// We need to include the members from the base interface's vtable at the start
/// of the VTable definition.
pub __base: nsISupportsVTable,
/* readonly attribute long effectiveContentSandboxLevel; */
pub GetEffectiveContentSandboxLevel: unsafe extern "system" fn (this: *const mozISandboxSettings, aEffectiveContentSandboxLevel: *mut i32) -> ::nserror::nsresult,
/* readonly attribute long contentWin32kLockdownState; */
pub GetContentWin32kLockdownState: unsafe extern "system" fn (this: *const mozISandboxSettings, aContentWin32kLockdownState: *mut i32) -> ::nserror::nsresult,
/* readonly attribute AString contentWin32kLockdownStateString; */
pub GetContentWin32kLockdownStateString: unsafe extern "system" fn (this: *const mozISandboxSettings, aContentWin32kLockdownStateString: *mut ::nsstring::nsAString) -> ::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 mozISandboxSettings {
/// `readonly attribute long effectiveContentSandboxLevel;`
#[inline]
pub unsafe fn GetEffectiveContentSandboxLevel(&self, aEffectiveContentSandboxLevel: *mut i32) -> ::nserror::nsresult {
((*self.vtable).GetEffectiveContentSandboxLevel)(self, aEffectiveContentSandboxLevel)
}
/// `readonly attribute long contentWin32kLockdownState;`
#[inline]
pub unsafe fn GetContentWin32kLockdownState(&self, aContentWin32kLockdownState: *mut i32) -> ::nserror::nsresult {
((*self.vtable).GetContentWin32kLockdownState)(self, aContentWin32kLockdownState)
}
/// `readonly attribute AString contentWin32kLockdownStateString;`
#[inline]
pub unsafe fn GetContentWin32kLockdownStateString(&self, aContentWin32kLockdownStateString: *mut ::nsstring::nsAString) -> ::nserror::nsresult {
((*self.vtable).GetContentWin32kLockdownStateString)(self, aContentWin32kLockdownStateString)
}
}