Built artifacts of de05244 [ci skip]

internals/api/src/uniffi_bindgen/bindings/swift/test.rs.html

@@ -383,7 +383,7 @@
     <span class="kw">if </span>!options.show_compiler_messages {
         <span class="comment">// This prevents most compiler messages, but not remarks
         </span>command.arg(<span class="string">&quot;-suppress-warnings&quot;</span>);
-        <span class="comment">// This gets the remarks.  Note: swift will eventually get a `-supress-remarks` argument,
+        <span class="comment">// This gets the remarks.  Note: swift will eventually get a `-suppress-remarks` argument,
         // maybe we can eventually move to that
         </span>command.stderr(Stdio::null());
     }

internals/api/src/uniffi_bindgen/interface/mod.rs.html

@@ -1804,7 +1804,7 @@
         <span class="self">self</span>.iter_user_ffi_function_definitions()
             .cloned()
             .chain(<span class="self">self</span>.iter_rust_buffer_ffi_function_definitions())
-            .chain(<span class="self">self</span>.iter_futures_ffi_function_definitons())
+            .chain(<span class="self">self</span>.iter_futures_ffi_function_definitions())
             .chain(<span class="self">self</span>.iter_checksum_ffi_functions())
             .chain([<span class="self">self</span>.ffi_uniffi_contract_version()])
     }
@@ -1853,7 +1853,7 @@
     }
 
     <span class="doccomment">/// List all FFI functions definitions for async functionality.
-    </span><span class="kw">pub fn </span>iter_futures_ffi_function_definitons(<span class="kw-2">&amp;</span><span class="self">self</span>) -&gt; <span class="kw">impl </span>Iterator&lt;Item = FfiFunction&gt; + <span class="lifetime">&#39;_ </span>{
+    </span><span class="kw">pub fn </span>iter_futures_ffi_function_definitions(<span class="kw-2">&amp;</span><span class="self">self</span>) -&gt; <span class="kw">impl </span>Iterator&lt;Item = FfiFunction&gt; + <span class="lifetime">&#39;_ </span>{
         <span class="kw">let </span>all_possible_return_ffi_types = [
             <span class="prelude-val">Some</span>(FfiType::UInt8),
             <span class="prelude-val">Some</span>(FfiType::Int8),

internals/api/src/uniffi_bindgen/library_mode.rs.html

@@ -422,10 +422,10 @@
 
 <span class="comment">// If `library_path` is a C dynamic library, return its name
 </span><span class="kw">pub fn </span>calc_cdylib_name(library_path: <span class="kw-2">&amp;</span>Utf8Path) -&gt; <span class="prelude-ty">Option</span>&lt;<span class="kw-2">&amp;</span>str&gt; {
-    <span class="kw">let </span>cdylib_extentions = [<span class="string">&quot;.so&quot;</span>, <span class="string">&quot;.dll&quot;</span>, <span class="string">&quot;.dylib&quot;</span>];
+    <span class="kw">let </span>cdylib_extensions = [<span class="string">&quot;.so&quot;</span>, <span class="string">&quot;.dll&quot;</span>, <span class="string">&quot;.dylib&quot;</span>];
     <span class="kw">let </span>filename = library_path.file_name()<span class="question-mark">?</span>;
     <span class="kw">let </span>filename = filename.strip_prefix(<span class="string">&quot;lib&quot;</span>).unwrap_or(filename);
-    <span class="kw">for </span>ext <span class="kw">in </span>cdylib_extentions {
+    <span class="kw">for </span>ext <span class="kw">in </span>cdylib_extensions {
         <span class="kw">if let </span><span class="prelude-val">Some</span>(f) = filename.strip_suffix(ext) {
             <span class="kw">return </span><span class="prelude-val">Some</span>(f);
         }

internals/api/src/uniffi_macros/error.rs.html

@@ -352,7 +352,7 @@
 
 <span class="comment">// FfiConverters for &quot;flat errors&quot;
 //
-// These are errors where we only lower the to_string() value, rather than any assocated data.
+// These are errors where we only lower the to_string() value, rather than any associated data.
 // We lower the to_string() value unconditionally, whether the enum has associated data or not.
 </span><span class="kw">fn </span>flat_error_ffi_converter_impl(
     ident: <span class="kw-2">&amp;</span>Ident,

internals/api/uniffi/ffi/fn.rust_call.html

@@ -3,7 +3,7 @@
     R: <a class="trait" href="../trait.FfiDefault.html" title="trait uniffi::FfiDefault">FfiDefault</a>,</span></code></pre><details class="toggle top-doc" open><summary class="hideme"><span>Expand description</span></summary><div class="docblock"><p>Handle a scaffolding calls</p>
 <p><code>callback</code> is responsible for making the actual Rust call and returning a special result type:</p>
 <ul>
-<li>For successfull calls, return <code>Ok(value)</code></li>
+<li>For successful calls, return <code>Ok(value)</code></li>
 <li>For errors that should be translated into thrown exceptions in the foreign code, serialize
 the error into a <code>RustBuffer</code>, then return <code>Ok(buf)</code></li>
 <li>The success type, must implement <code>FfiDefault</code>.</li>

internals/api/uniffi/ffi/rustcalls/fn.rust_call.html

@@ -3,7 +3,7 @@
     R: <a class="trait" href="../../trait.FfiDefault.html" title="trait uniffi::FfiDefault">FfiDefault</a>,</span></code></pre><details class="toggle top-doc" open><summary class="hideme"><span>Expand description</span></summary><div class="docblock"><p>Handle a scaffolding calls</p>
 <p><code>callback</code> is responsible for making the actual Rust call and returning a special result type:</p>
 <ul>
-<li>For successfull calls, return <code>Ok(value)</code></li>
+<li>For successful calls, return <code>Ok(value)</code></li>
 <li>For errors that should be translated into thrown exceptions in the foreign code, serialize
 the error into a <code>RustBuffer</code>, then return <code>Ok(buf)</code></li>
 <li>The success type, must implement <code>FfiDefault</code>.</li>

internals/api/uniffi/fn.rust_call.html

@@ -3,7 +3,7 @@
     R: <a class="trait" href="trait.FfiDefault.html" title="trait uniffi::FfiDefault">FfiDefault</a>,</span></code></pre><details class="toggle top-doc" open><summary class="hideme"><span>Expand description</span></summary><div class="docblock"><p>Handle a scaffolding calls</p>
 <p><code>callback</code> is responsible for making the actual Rust call and returning a special result type:</p>
 <ul>
-<li>For successfull calls, return <code>Ok(value)</code></li>
+<li>For successful calls, return <code>Ok(value)</code></li>
 <li>For errors that should be translated into thrown exceptions in the foreign code, serialize
 the error into a <code>RustBuffer</code>, then return <code>Ok(buf)</code></li>
 <li>The success type, must implement <code>FfiDefault</code>.</li>

print.html

@@ -257,7 +257,7 @@ <h2 id="why-not"><a class="header" href="#why-not">Why Not?</a></h2>
 <p>And top brass would like you to expose this <em>business-critical</em> operation to Kotlin and Swift.<br />
 <strong>Don't panic!</strong> We will show you how do that using UniFFI.</p>
 <div style="break-before: page; page-break-before: always;"></div><h1 id="prerequisites"><a class="header" href="#prerequisites">Prerequisites</a></h1>
-<h2 id="add-uniffi-as-a-dependency-and-build-depedency"><a class="header" href="#add-uniffi-as-a-dependency-and-build-depedency">Add <code>uniffi</code> as a dependency and build-depedency</a></h2>
+<h2 id="add-uniffi-as-a-dependency-and-build-dependency"><a class="header" href="#add-uniffi-as-a-dependency-and-build-dependency">Add <code>uniffi</code> as a dependency and build-dependency</a></h2>
 <p>In your crate's <code>Cargo.toml</code> add:</p>
 <pre><code class="language-toml">[dependencies]
 uniffi = { version = &quot;[latest-version]&quot; }
@@ -954,7 +954,7 @@ <h2 id="concurrent-access"><a class="header" href="#concurrent-access">Concurren
 <div style="break-before: page; page-break-before: always;"></div><h1 id="callback-interfaces"><a class="header" href="#callback-interfaces">Callback interfaces</a></h1>
 <p>Callback interfaces are a special implementation of
 <a href="udl/../foreign_traits.html">Rust traits implemented by foreign languages</a>.</p>
-<p>These are described in both UDL and proc-macros as an explict &quot;callback interface&quot;.
+<p>These are described in both UDL and proc-macros as an explicit &quot;callback interface&quot;.
 They are (soft) deprecated, remain now for backwards compatibility, but probably
 should be avoided.</p>
 <p>This document describes the differences from regular traits.</p>
@@ -1014,7 +1014,7 @@ <h2 id="types-from-procmacros-in-this-crate"><a class="header" href="#types-from
   boolean bool_val;
 };
 </code></pre>
-<p>Inside another crate,  <code>consuming_crate</code>, you'd like to use this dictionary.
+<p>Inside another crate, <code>consuming_crate</code>, you'd like to use this dictionary.
 Inside <code>consuming_crate</code>'s UDL file you can reference <code>DemoDict</code> by using a
 <code>typedef</code> with an <code>External</code> attribute, as shown below.</p>
 <pre><code class="language-idl">[External=&quot;demo_crate&quot;]
@@ -1052,7 +1052,7 @@ <h2 id="external-procmacro-types"><a class="header" href="#external-procmacro-ty
 <li>if <code>DemoDict</code> is implemented by a procmacro in <code>demo_crate</code>, you'd use <code>[ExternalExport=...]</code></li>
 <li>for <code>DemoInterface</code> you'd use <code>[ExternalInterfaceExport=...]</code></li>
 </ul>
-<p>For types defined by procmacros in <em>this</em> crate, see the []<code>[Rust=...]</code> attribute](../ext_types.md)</p>
+<p>For types defined by procmacros in <em>this</em> crate, see the <a href="udl/./ext_types.html">attribute <code>[Rust=...]</code></a></p>
 <h2 id="foreign-bindings"><a class="header" href="#foreign-bindings">Foreign bindings</a></h2>
 <p>The foreign bindings will also need to know how to access the external type,
 which varies slightly for each language:</p>
@@ -1300,7 +1300,7 @@ <h2 id="docstrings-in-generated-python-bindings"><a class="header" href="#docstr
 because at this time, that documentation tends to conflate the UniFFI type model and the
 description of how foreign bindings use that type model. For example, the documentation for
 a UDL interface describes both how it is defined in UDL and how Swift and Kotlin might use
-that interface. The latter is relevent even if you define the interface using proc-macros
+that interface. The latter is relevant even if you define the interface using proc-macros
 instead of in UDL.</p>
 <p><strong>⚠ Warning ⚠</strong> This facility is relatively new, so things may change often. However, this remains
 true for all of UniFFI, so proceed with caution and the knowledge that things may break in the future.</p>

proc_macro/index.html

@@ -183,7 +183,7 @@ <h1 id="procedural-macros-attributes-and-derives"><a class="header" href="#proce
 because at this time, that documentation tends to conflate the UniFFI type model and the
 description of how foreign bindings use that type model. For example, the documentation for
 a UDL interface describes both how it is defined in UDL and how Swift and Kotlin might use
-that interface. The latter is relevent even if you define the interface using proc-macros
+that interface. The latter is relevant even if you define the interface using proc-macros
 instead of in UDL.</p>
 <p><strong>⚠ Warning ⚠</strong> This facility is relatively new, so things may change often. However, this remains
 true for all of UniFFI, so proceed with caution and the knowledge that things may break in the future.</p>

tutorial/Prerequisites.html

@@ -172,7 +172,7 @@ <h1 class="menu-title">The UniFFI user guide</h1>
                 <div id="content" class="content">
                     <main>
                         <h1 id="prerequisites"><a class="header" href="#prerequisites">Prerequisites</a></h1>
-<h2 id="add-uniffi-as-a-dependency-and-build-depedency"><a class="header" href="#add-uniffi-as-a-dependency-and-build-depedency">Add <code>uniffi</code> as a dependency and build-depedency</a></h2>
+<h2 id="add-uniffi-as-a-dependency-and-build-dependency"><a class="header" href="#add-uniffi-as-a-dependency-and-build-dependency">Add <code>uniffi</code> as a dependency and build-dependency</a></h2>
 <p>In your crate's <code>Cargo.toml</code> add:</p>
 <pre><code class="language-toml">[dependencies]
 uniffi = { version = &quot;[latest-version]&quot; }

udl/callback_interfaces.html

@@ -174,7 +174,7 @@ <h1 class="menu-title">The UniFFI user guide</h1>
                         <h1 id="callback-interfaces"><a class="header" href="#callback-interfaces">Callback interfaces</a></h1>
 <p>Callback interfaces are a special implementation of
 <a href="../foreign_traits.html">Rust traits implemented by foreign languages</a>.</p>
-<p>These are described in both UDL and proc-macros as an explict &quot;callback interface&quot;.
+<p>These are described in both UDL and proc-macros as an explicit &quot;callback interface&quot;.
 They are (soft) deprecated, remain now for backwards compatibility, but probably
 should be avoided.</p>
 <p>This document describes the differences from regular traits.</p>

udl/ext_types_external.html

@@ -179,7 +179,7 @@ <h1 id="declaring-external-types"><a class="header" href="#declaring-external-ty
   boolean bool_val;
 };
 </code></pre>
-<p>Inside another crate,  <code>consuming_crate</code>, you'd like to use this dictionary.
+<p>Inside another crate, <code>consuming_crate</code>, you'd like to use this dictionary.
 Inside <code>consuming_crate</code>'s UDL file you can reference <code>DemoDict</code> by using a
 <code>typedef</code> with an <code>External</code> attribute, as shown below.</p>
 <pre><code class="language-idl">[External=&quot;demo_crate&quot;]
@@ -217,7 +217,7 @@ <h2 id="external-procmacro-types"><a class="header" href="#external-procmacro-ty
 <li>if <code>DemoDict</code> is implemented by a procmacro in <code>demo_crate</code>, you'd use <code>[ExternalExport=...]</code></li>
 <li>for <code>DemoInterface</code> you'd use <code>[ExternalInterfaceExport=...]</code></li>
 </ul>
-<p>For types defined by procmacros in <em>this</em> crate, see the []<code>[Rust=...]</code> attribute](../ext_types.md)</p>
+<p>For types defined by procmacros in <em>this</em> crate, see the <a href="./ext_types.html">attribute <code>[Rust=...]</code></a></p>
 <h2 id="foreign-bindings"><a class="header" href="#foreign-bindings">Foreign bindings</a></h2>
 <p>The foreign bindings will also need to know how to access the external type,
 which varies slightly for each language:</p>