Rewrap all comments to 100 line width (#9490)

* reformat everything again

* manual formatting

* last manual fix

* Fix build

substrate/client/executor/common/src/runtime_blob/mod.rs

@@ -26,27 +26,28 @@
 //!
 //! To give you some examples:
 //!
-//! - wasmi allows reaching to non-exported mutable globals so that we could reset them.
-//!   Wasmtime doesn’t support that.
+//! - wasmi allows reaching to non-exported mutable globals so that we could reset them. Wasmtime
+//!   doesn’t support that.
 //!
 //!   We need to reset the globals because when we
 //!   execute the Substrate Runtime, we do not drop and create the instance anew, instead
 //!   we restore some selected parts of the state.
 //!
-//! - stack depth metering can be performed via instrumentation or deferred to the engine and say
-//!   be added directly in machine code. Implementing this in machine code is rather cumbersome so
+//! - stack depth metering can be performed via instrumentation or deferred to the engine and say be
+//!   added directly in machine code. Implementing this in machine code is rather cumbersome so
 //!   instrumentation looks like a good solution.
 //!
 //!   Stack depth metering is needed to make a wasm blob
-//!   execution deterministic, which in turn is needed by the Parachain Validation Function in Polkadot.
+//!   execution deterministic, which in turn is needed by the Parachain Validation Function in
+//! Polkadot.
 //!
 //! ## Inspection
 //!
 //! Inspection of a wasm module may be needed to extract some useful information, such as to extract
 //! data segment snapshot, which is helpful for quickly restoring the initial state of instances.
 //! Inspection can be also useful to prove that a wasm module possesses some properties, such as,
-//! is free of any floating point operations, which is a useful step towards making instances produced
-//! from such a module deterministic.
+//! is free of any floating point operations, which is a useful step towards making instances
+//! produced from such a module deterministic.
 
 mod data_segments_snapshot;
 mod globals_snapshot;

substrate/client/executor/common/src/runtime_blob/runtime_blob.rs

@@ -72,11 +72,13 @@ impl RuntimeBlob {
 		export_mutable_globals(&mut self.raw_module, "exported_internal_global");
 	}
 
-	/// Run a pass that instrument this module so as to introduce a deterministic stack height limit.
+	/// Run a pass that instrument this module so as to introduce a deterministic stack height
+	/// limit.
 	///
 	/// It will introduce a global mutable counter. The instrumentation will increase the counter
 	/// according to the "cost" of the callee. If the cost exceeds the `stack_depth_limit` constant,
-	/// the instrumentation will trap. The counter will be decreased as soon as the the callee returns.
+	/// the instrumentation will trap. The counter will be decreased as soon as the the callee
+	/// returns.
 	///
 	/// The stack cost of a function is computed based on how much locals there are and the maximum
 	/// depth of the wasm operand stack.
@@ -89,7 +91,8 @@ impl RuntimeBlob {
 		Ok(Self { raw_module: injected_module })
 	}
 
-	/// Perform an instrumentation that makes sure that a specific function `entry_point` is exported
+	/// Perform an instrumentation that makes sure that a specific function `entry_point` is
+	/// exported
 	pub fn entry_point_exists(&self, entry_point: &str) -> bool {
 		self.raw_module
 			.export_section()

substrate/client/executor/common/src/wasm_runtime.rs

@@ -98,7 +98,8 @@ pub trait WasmInstance: Send {
 	///
 	/// This is meant to be the starting address of the memory mapped area for the linear memory.
 	///
-	/// This function is intended only for a specific test that measures physical memory consumption.
+	/// This function is intended only for a specific test that measures physical memory
+	/// consumption.
 	fn linear_memory_base_ptr(&self) -> Option<*const u8> {
 		None
 	}