This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch gh-pages
in repository https://gitbox.apache.org/repos/asf/arrow-nanoarrow.git
The following commit(s) were added to refs/heads/gh-pages by this push:
new 7a6d8c9 update documentation for tag dev
7a6d8c9 is described below
commit 7a6d8c91d66b189ea4d1e4fb18630d3c6cad9a5a
Author: GitHub Actions <[email protected]>
AuthorDate: Tue Aug 15 14:55:52 2023 +0000
update documentation for tag dev
---
dev/_sources/getting-started_generated.rst.txt | 6 +++---
dev/getting-started.html | 6 +++---
dev/getting-started_generated.html | 6 +++---
dev/r/pkgdown.yml | 2 +-
dev/reference/ipc.html | 2 +-
dev/searchindex.js | 2 +-
6 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/dev/_sources/getting-started_generated.rst.txt
b/dev/_sources/getting-started_generated.rst.txt
index 43180ce..f63eddf 100644
--- a/dev/_sources/getting-started_generated.rst.txt
+++ b/dev/_sources/getting-started_generated.rst.txt
@@ -187,7 +187,7 @@ nanoarrow implementation.
First, let’s discuss the ``ArrowSchema`` and the ``ArrowArray``. You can
think of an ``ArrowSchema`` as an expression of a data type, whereas an
-``ArrowArray`` is the data itself. These structures accomodate nested
+``ArrowArray`` is the data itself. These structures accommodate nested
types: columns are encoded in the ``children`` member of each. You
always need to know the data type of an ``ArrowArray`` before accessing
its contents. In our case we only operate on arrays of one type
@@ -321,7 +321,7 @@ integration.
After saving ``CMakeLists.txt``, you may have to close and re-open the
``linesplitter`` directory in VSCode to activate the CMake integration.
-From the command pallete (i.e., Control/Command-Shift-P), choose
+From the command palette (i.e., Control/Command-Shift-P), choose
**CMake: Build**. If all went well, you should see a few lines of output
indicating progress towards building and linking ``linesplitter``.
@@ -488,7 +488,7 @@ Then, add the following to your ``CMakeLists.txt``:
After you’re done, build the project again using the **CMake: Build**
command from the command palette. If all goes well, choose **CMake:
Refresh Tests** and then **Test: Run All Tests** from the command
-pallete to run them! You should see some output indiciating that tests
+palette to run them! You should see some output indicating that tests
ran successfully, or you can use VSCode’s “Testing” panel to visually
inspect which tests passed.
diff --git a/dev/getting-started.html b/dev/getting-started.html
index 21d444c..646b986 100644
--- a/dev/getting-started.html
+++ b/dev/getting-started.html
@@ -493,7 +493,7 @@ using the Arrow C data interface and a few conventions used
in the
nanoarrow implementation.</p>
<p>First, let’s discuss the <code class="docutils literal notranslate"><span
class="pre">ArrowSchema</span></code> and the <code class="docutils literal
notranslate"><span class="pre">ArrowArray</span></code>. You can
think of an <code class="docutils literal notranslate"><span
class="pre">ArrowSchema</span></code> as an expression of a data type, whereas
an
-<code class="docutils literal notranslate"><span
class="pre">ArrowArray</span></code> is the data itself. These structures
accomodate nested
+<code class="docutils literal notranslate"><span
class="pre">ArrowArray</span></code> is the data itself. These structures
accommodate nested
types: columns are encoded in the <code class="docutils literal
notranslate"><span class="pre">children</span></code> member of each. You
always need to know the data type of an <code class="docutils literal
notranslate"><span class="pre">ArrowArray</span></code> before accessing
its contents. In our case we only operate on arrays of one type
@@ -613,7 +613,7 @@ integration.</p>
</div>
<p>After saving <code class="docutils literal notranslate"><span
class="pre">CMakeLists.txt</span></code>, you may have to close and re-open the
<code class="docutils literal notranslate"><span
class="pre">linesplitter</span></code> directory in VSCode to activate the
CMake integration.
-From the command pallete (i.e., Control/Command-Shift-P), choose
+From the command palette (i.e., Control/Command-Shift-P), choose
<strong>CMake: Build</strong>. If all went well, you should see a few lines of
output
indicating progress towards building and linking <code class="docutils literal
notranslate"><span class="pre">linesplitter</span></code>.</p>
<div class="admonition note">
@@ -768,7 +768,7 @@ the complexity of your project grows.</p>
<p>After you’re done, build the project again using the <strong>CMake:
Build</strong>
command from the command palette. If all goes well, choose <strong>CMake:
Refresh Tests</strong> and then <strong>Test: Run All Tests</strong> from the
command
-pallete to run them! You should see some output indiciating that tests
+palette to run them! You should see some output indicating that tests
ran successfully, or you can use VSCode’s “Testing” panel to visually
inspect which tests passed.</p>
<div class="admonition note">
diff --git a/dev/getting-started_generated.html
b/dev/getting-started_generated.html
index 6c3cabe..4d17bd7 100644
--- a/dev/getting-started_generated.html
+++ b/dev/getting-started_generated.html
@@ -491,7 +491,7 @@ using the Arrow C data interface and a few conventions used
in the
nanoarrow implementation.</p>
<p>First, let’s discuss the <code class="docutils literal notranslate"><span
class="pre">ArrowSchema</span></code> and the <code class="docutils literal
notranslate"><span class="pre">ArrowArray</span></code>. You can
think of an <code class="docutils literal notranslate"><span
class="pre">ArrowSchema</span></code> as an expression of a data type, whereas
an
-<code class="docutils literal notranslate"><span
class="pre">ArrowArray</span></code> is the data itself. These structures
accomodate nested
+<code class="docutils literal notranslate"><span
class="pre">ArrowArray</span></code> is the data itself. These structures
accommodate nested
types: columns are encoded in the <code class="docutils literal
notranslate"><span class="pre">children</span></code> member of each. You
always need to know the data type of an <code class="docutils literal
notranslate"><span class="pre">ArrowArray</span></code> before accessing
its contents. In our case we only operate on arrays of one type
@@ -611,7 +611,7 @@ integration.</p>
</div>
<p>After saving <code class="docutils literal notranslate"><span
class="pre">CMakeLists.txt</span></code>, you may have to close and re-open the
<code class="docutils literal notranslate"><span
class="pre">linesplitter</span></code> directory in VSCode to activate the
CMake integration.
-From the command pallete (i.e., Control/Command-Shift-P), choose
+From the command palette (i.e., Control/Command-Shift-P), choose
<strong>CMake: Build</strong>. If all went well, you should see a few lines of
output
indicating progress towards building and linking <code class="docutils literal
notranslate"><span class="pre">linesplitter</span></code>.</p>
<div class="admonition note">
@@ -766,7 +766,7 @@ the complexity of your project grows.</p>
<p>After you’re done, build the project again using the <strong>CMake:
Build</strong>
command from the command palette. If all goes well, choose <strong>CMake:
Refresh Tests</strong> and then <strong>Test: Run All Tests</strong> from the
command
-pallete to run them! You should see some output indiciating that tests
+palette to run them! You should see some output indicating that tests
ran successfully, or you can use VSCode’s “Testing” panel to visually
inspect which tests passed.</p>
<div class="admonition note">
diff --git a/dev/r/pkgdown.yml b/dev/r/pkgdown.yml
index 244e9a1..d2213a5 100644
--- a/dev/r/pkgdown.yml
+++ b/dev/r/pkgdown.yml
@@ -2,5 +2,5 @@ pandoc: 2.9.2.1
pkgdown: 2.0.7
pkgdown_sha: ~
articles: {}
-last_built: 2023-08-14T17:55Z
+last_built: 2023-08-15T14:55Z
diff --git a/dev/reference/ipc.html b/dev/reference/ipc.html
index 3279a13..cd698d8 100644
--- a/dev/reference/ipc.html
+++ b/dev/reference/ipc.html
@@ -535,7 +535,7 @@ document.write(`
<span
id="_CPPv327ArrowIpcDecoderDecodeHeaderP15ArrowIpcDecoder15ArrowBufferViewP10ArrowError"></span><span
id="_CPPv227ArrowIpcDecoderDecodeHeaderP15ArrowIpcDecoder15ArrowBufferViewP10ArrowError"></span><span
id="ArrowIpcDecoderDecodeHeader__ArrowIpcDecoderP.ArrowBufferView.ArrowErrorP"></span><span
class="target"
id="group__nanoarrow__ipc_1gaa4ea4cae2cca86081b9279e481e4dab0"></span><a
class="reference internal" href="c.html#_CPPv414ArrowErrorCode"
title="ArrowErrorCode"><span class="n" [...]
<dd><p>Decode a message header. </p>
<p>Runs <a class="reference internal"
href="#group__nanoarrow__ipc_1ga02b0a558c785e952737182e04eba936d"><span
class="std std-ref">ArrowIpcDecoderPeekHeader()</span></a> to ensure data is
sufficiently large and decodes the content of the message header. If data
contains a schema message, decoder.endianness and decoder.feature_flags is set
and <a class="reference internal"
href="#group__nanoarrow__ipc_1gab56730acfeaad71f0b31e0616c3cac02"><span
class="std std-ref">ArrowIpcDecoderDecodeSchem [...]
-<p>In almost all cases this should be preceeded by a call to <a
class="reference internal"
href="#group__nanoarrow__ipc_1ga5d19acbf708ca5b4b7cbe32fa81378a6"><span
class="std std-ref">ArrowIpcDecoderVerifyHeader()</span></a> to ensure decoding
does not access data outside of the specified buffer.</p>
+<p>In almost all cases this should be preceded by a call to <a
class="reference internal"
href="#group__nanoarrow__ipc_1ga5d19acbf708ca5b4b7cbe32fa81378a6"><span
class="std std-ref">ArrowIpcDecoderVerifyHeader()</span></a> to ensure decoding
does not access data outside of the specified buffer.</p>
<p>Returns EINVAL if the content of the message cannot be decoded or ENOTSUP
if the content of the message uses features not supported by this library. </p>
</dd></dl>
diff --git a/dev/searchindex.js b/dev/searchindex.js
index 609323e..78b299e 100644
--- a/dev/searchindex.js
+++ b/dev/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["getting-started", "getting-started_generated",
"index", "reference/c", "reference/cpp", "reference/device", "reference/index",
"reference/ipc", "reference/r"], "filenames": ["getting-started.rst",
"getting-started_generated.rst", "index.rst", "reference/c.rst",
"reference/cpp.rst", "reference/device.rst", "reference/index.rst",
"reference/ipc.rst", "reference/r.rst"], "titles": ["Getting started with
nanoarrow", "Getting started with nanoarrow", "nanoarrow" [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["getting-started", "getting-started_generated",
"index", "reference/c", "reference/cpp", "reference/device", "reference/index",
"reference/ipc", "reference/r"], "filenames": ["getting-started.rst",
"getting-started_generated.rst", "index.rst", "reference/c.rst",
"reference/cpp.rst", "reference/device.rst", "reference/index.rst",
"reference/ipc.rst", "reference/r.rst"], "titles": ["Getting started with
nanoarrow", "Getting started with nanoarrow", "nanoarrow" [...]
\ No newline at end of file
