mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-04-26 08:47:57 +00:00
Make use of cfg(doc) in sp-runtime-interface (#4673)
By using `cfg(doc)`, we can generate docs for modules which are only available from `no_std`. This drastically improves the documentation for the developers.
This commit is contained in:
committed by
Shawn Tabrizi
parent
26fa5193cd
commit
96cd57a695
@@ -49,6 +49,9 @@ pub trait IntoPreallocatedFFIValue: RIType {
|
||||
}
|
||||
|
||||
/// Something that can be created from a ffi value.
|
||||
/// Implementations are safe to assume that the `arg` given to `from_ffi_value`
|
||||
/// is only generated by the corresponding [`wasm::IntoFFIValue`](crate::wasm::IntoFFIValue)
|
||||
/// implementation.
|
||||
pub trait FromFFIValue: RIType {
|
||||
/// As `Self` can be an unsized type, it needs to be represented by a sized type at the host.
|
||||
/// This `SelfInstance` is the sized type.
|
||||
|
||||
@@ -25,10 +25,10 @@
|
||||
//! # Using a type in a runtime interface
|
||||
//!
|
||||
//! Any type that should be used in a runtime interface as argument or return value needs to
|
||||
//! implement [`RIType`]. The associated type `FFIType` is the type that is used in the FFI
|
||||
//! function to represent the actual type. For example `[T]` is represented by an `u64`. The slice
|
||||
//! pointer and the length will be mapped to an `u64` value. For more information, see the
|
||||
//! implementation of [`RIType`] for `T`. The FFI function definition is used when calling from
|
||||
//! implement [`RIType`]. The associated type [`FFIType`](RIType::FFIType) is the type that is used
|
||||
//! in the FFI function to represent the actual type. For example `[T]` is represented by an `u64`.
|
||||
//! The slice pointer and the length will be mapped to an `u64` value. For more information see
|
||||
//! this [table](#ffi-type-and-conversion). The FFI function definition is used when calling from
|
||||
//! the wasm runtime into the node.
|
||||
//!
|
||||
//! Traits are used to convert from a type to the corresponding [`RIType::FFIType`].
|
||||
@@ -265,7 +265,7 @@ pub use codec;
|
||||
pub(crate) mod impls;
|
||||
#[cfg(feature = "std")]
|
||||
pub mod host;
|
||||
#[cfg(not(feature = "std"))]
|
||||
#[cfg(any(not(feature = "std"), doc))]
|
||||
pub mod wasm;
|
||||
pub mod pass_by;
|
||||
|
||||
|
||||
@@ -26,7 +26,8 @@ use sp_std::cell::Cell;
|
||||
///
|
||||
/// It is unsafe behavior to call `Something::into_ffi_value().get()` and take this as input for
|
||||
/// `from_ffi_value`. Implementations are safe to assume that the `arg` given to `from_ffi_value`
|
||||
/// is only generated by the corresponding `host::IntoFFIValue` implementation.
|
||||
/// is only generated by the corresponding [`host::IntoFFIValue`](crate::host::IntoFFIValue)
|
||||
/// implementation.
|
||||
pub trait FromFFIValue: Sized + RIType {
|
||||
/// Create `Self` from the given ffi value.
|
||||
fn from_ffi_value(arg: Self::FFIType) -> Self;
|
||||
|
||||
Reference in New Issue
Block a user