Copy as Markdown
Other Tools
//
// DO NOT EDIT. THIS FILE IS GENERATED FROM $SRCDIR/toolkit/components/remote/nsIRemoteService.idl
//
/// `interface nsIRemoteService : 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 nsIRemoteService {
vtable: &'static nsIRemoteServiceVTable,
/// 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 nsIRemoteService.
unsafe impl XpCom for nsIRemoteService {
const IID: nsIID = nsID(0xf4ef671b, 0x838c, 0x48fd,
[0xbc, 0x44, 0x0f, 0x6c, 0xf6, 0x3b, 0xce, 0x91]);
}
// 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 nsIRemoteService {
#[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 nsIRemoteService.
// 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 nsIRemoteServiceCoerce {
/// Cheaply cast a value of this type from a `nsIRemoteService`.
fn coerce_from(v: &nsIRemoteService) -> &Self;
}
// The trivial implementation: We can obviously coerce ourselves to ourselves.
impl nsIRemoteServiceCoerce for nsIRemoteService {
#[inline]
fn coerce_from(v: &nsIRemoteService) -> &Self {
v
}
}
impl nsIRemoteService {
/// Cast this `nsIRemoteService` to one of its base interfaces.
#[inline]
pub fn coerce<T: nsIRemoteServiceCoerce>(&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 nsIRemoteService {
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> nsIRemoteServiceCoerce for T {
#[inline]
fn coerce_from(v: &nsIRemoteService) -> &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 nsIRemoteService
// 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 nsIRemoteServiceVTable {
/// We need to include the members from the base interface's vtable at the start
/// of the VTable definition.
pub __base: nsISupportsVTable,
/* void sendCommandLine (in ACString aProfile, in Array<ACString> aArgs, [optional] in boolean aRaise); */
pub SendCommandLine: unsafe extern "system" fn (this: *const nsIRemoteService, aProfile: *const ::nsstring::nsACString, aArgs: *const thin_vec::ThinVec<::nsstring::nsCString>, aRaise: bool) -> ::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 nsIRemoteService {
/// ```text
/// /**
/// * Sends command line arguments to another running instance.
/// * Note that the other instance must be on the same update channel. The
/// * profile argument should be the full path to the root profile folder. The
/// * other instance must also have not disabled the remoting service (e.g. with
/// * -no-remote on the command line).
/// *
/// * @param aProfile
/// * The profile the running instance is using.
/// * @param aArgs
/// * The command line arguments to send. Don't include the initial
/// * binary path argument.
/// * @param aRaise
/// * Whether the target instance's window should be brought to the
/// * foreground. The actual effect of this is platform-dependent; see
/// * comments in platform-specific implementations for further
/// * information.
/// * @throws NS_ERROR_NOT_AVAILABLE if no running instance was found.
/// */
/// ```
///
/// `void sendCommandLine (in ACString aProfile, in Array<ACString> aArgs, [optional] in boolean aRaise);`
#[inline]
pub unsafe fn SendCommandLine(&self, aProfile: *const ::nsstring::nsACString, aArgs: *const thin_vec::ThinVec<::nsstring::nsCString>, aRaise: bool) -> ::nserror::nsresult {
((*self.vtable).SendCommandLine)(self, aProfile, aArgs, aRaise)
}
}