This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/datafusion.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 68a1326c14 Publish built docs triggered by
878b87911ec9c35aa74244a8b7535c6aced8ff20
68a1326c14 is described below
commit 68a1326c149e42533dbde8da41f8e99c4fcbe0fb
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Sun Mar 22 12:21:22 2026 +0000
Publish built docs triggered by 878b87911ec9c35aa74244a8b7535c6aced8ff20
---
.../development_environment.md.txt | 41 ++++++++++++++++---
_sources/contributor-guide/index.md.txt | 19 ++++++++-
_sources/contributor-guide/testing.md.txt | 31 ++++++++++++++
contributor-guide/development_environment.html | 47 ++++++++++++++++++----
contributor-guide/index.html | 17 +++++++-
contributor-guide/testing.html | 27 +++++++++++++
searchindex.js | 2 +-
7 files changed, 166 insertions(+), 18 deletions(-)
diff --git a/_sources/contributor-guide/development_environment.md.txt
b/_sources/contributor-guide/development_environment.md.txt
index 77910b3540..4d04d38c74 100644
--- a/_sources/contributor-guide/development_environment.md.txt
+++ b/_sources/contributor-guide/development_environment.md.txt
@@ -21,7 +21,38 @@
This section describes how you can get started at developing DataFusion.
-## Windows setup
+## Quick Start
+
+For the fastest path to a working local environment, follow these steps
+from the repository root:
+
+```shell
+# 1. Install Rust (https://rust-lang.org/tools/install/) and verify the active
toolchain with
+rustup show
+
+# 2. Install protoc 3.15+ (see details below)
+protoc --version
+
+# 3. Download test data used by examples and many tests
+git submodule update --init --recursive
+
+# 4. Build the workspace
+cargo build
+
+# 5. Verify that Rust integration tests can be run
+cargo test -p datafusion --test parquet_integration
+
+# 6. Verify that sqllogictests can run
+cargo test --profile=ci --test sqllogictests
+```
+
+Notes:
+
+- The pinned Rust version is defined in `rust-toolchain.toml`.
+- `protoc` is required to compile DataFusion from source.
+- Some tests and examples rely on git submodule data being present locally.
+
+## Windows Setup
```shell
wget
https://az792536.vo.msecnd.net/vms/VMBuild_20190311/VirtualBox/MSEdge/MSEdge.Win10.VirtualBox.zip
@@ -34,7 +65,7 @@ cargo build
DataFusion has support for [dev containers](https://containers.dev/) which may
be used for
developing DataFusion in an isolated environment either locally or remote if
desired. Using dev containers for developing
-DataFusion is not a requirement by any means but is available for those where
doing local development could be tricky
+DataFusion is not a requirement but is available where doing local development
could be tricky
such as with Windows and WSL2, those with older hardware, etc.
For specific details on IDE support for dev containers see the documentation
for [Visual Studio
Code](https://code.visualstudio.com/docs/devcontainers/containers),
@@ -42,11 +73,11 @@ For specific details on IDE support for dev containers see
the documentation for
[Rust
Rover](https://www.jetbrains.com/help/rust/connect-to-devcontainer.html), and
[GitHub
Codespaces](https://docs.github.com/en/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers).
-## Protoc Installation
+## `protoc` Installation
Compiling DataFusion from sources requires an installed version of the
protobuf compiler, `protoc`.
-On most platforms this can be installed from your system's package manager
+On most platforms this can be installed from your system's package manager.
For example:
```
# Ubuntu
@@ -71,7 +102,7 @@ libprotoc 3.15.0
Alternatively a binary release can be downloaded from the [Release
Page](https://github.com/protocolbuffers/protobuf/releases) or [built from
source](https://github.com/protocolbuffers/protobuf/blob/main/src/README.md).
-## Bootstrap environment
+## Bootstrap Environment
DataFusion is written in Rust and it uses a standard rust toolkit:
diff --git a/_sources/contributor-guide/index.md.txt
b/_sources/contributor-guide/index.md.txt
index 2ee8a2aaac..4ace4be494 100644
--- a/_sources/contributor-guide/index.md.txt
+++ b/_sources/contributor-guide/index.md.txt
@@ -32,8 +32,10 @@ community as well as get more familiar with Rust and the
relevant codebases.
## Development Environment
-Setup your development environment [here](development_environment.md), and
learn
-how to test the code [here](testing.md).
+Start with the [Development Environment Quick
Start](development_environment.md#quick-start).
+
+For more detail, see the full [development environment
guide](development_environment.md)
+and the [testing guide](testing.md).
## Finding and Creating Issues to Work On
@@ -99,6 +101,19 @@ If you are concerned that a larger design will be lost in a
string of small PRs,
Note all commits in a PR are squashed when merged to the `main` branch so
there is one commit per PR after merge.
+## Before Submitting a PR
+
+Before submitting a PR, run the standard non-functional checks. PRs must pass
+before merge.
+
+```bash
+./dev/rust_lint.sh
+# use `--write` to automatically fix some formatting and lint errors
+# ./dev/rust_lint.sh --write --allow-dirty
+```
+
+You should also run any relevant commands from the [testing quick
start](testing.md#testing-quick-start).
+
## Conventional Commits & Labeling PRs
We generate change logs for each release using an automated process that will
categorize PRs based on the title
diff --git a/_sources/contributor-guide/testing.md.txt
b/_sources/contributor-guide/testing.md.txt
index 43b727211d..6b8e4568ec 100644
--- a/_sources/contributor-guide/testing.md.txt
+++ b/_sources/contributor-guide/testing.md.txt
@@ -23,6 +23,37 @@ Tests are critical to ensure that DataFusion is working
properly and
is not accidentally broken during refactorings. All new features
should have test coverage and the entire test suite is run as part of CI.
+## Testing Quick Start
+
+While developing a feature or bug fix, best practice is to run the smallest set
+of tests that gives confidence for your change, then expand as needed.
+
+Initially, run the tests in the crates you changed. For example, if you made
changes
+to files in `datafusion-optimizer/src`, run the corresponding crate tests:
+
+```shell
+cargo test -p datafusion-optimizer
+```
+
+Then, run the `sqllogictest` suite, which provides a strong speed–coverage
tradeoff for development: it runs quickly while offering broad regression
coverage across most SQL behavior in DataFusion.
+
+```shell
+cargo test --profile=ci --test sqllogictests
+```
+
+Finally, before submitting a PR, run the tests for the core `datafusion` and
+`datafusion-cli` crates:
+
+```shell
+cargo test -p datafusion
+cargo test -p datafusion-cli
+```
+
+Some integration tests require optional external services such as Docker-backed
+containers and may skip when unavailable.
+
+## Testing Overview
+
DataFusion has several levels of tests in its [Test Pyramid] and tries to
follow
the Rust standard [Testing Organization] described in [The Book].
diff --git a/contributor-guide/development_environment.html
b/contributor-guide/development_environment.html
index 7321cfbda8..e135e10d84 100644
--- a/contributor-guide/development_environment.html
+++ b/contributor-guide/development_environment.html
@@ -420,8 +420,38 @@
<section id="development-environment">
<h1>Development Environment<a class="headerlink"
href="#development-environment" title="Link to this heading">#</a></h1>
<p>This section describes how you can get started at developing DataFusion.</p>
+<section id="quick-start">
+<h2>Quick Start<a class="headerlink" href="#quick-start" title="Link to this
heading">#</a></h2>
+<p>For the fastest path to a working local environment, follow these steps
+from the repository root:</p>
+<div class="highlight-shell notranslate"><div
class="highlight"><pre><span></span><span class="c1"># 1. Install Rust
(https://rust-lang.org/tools/install/) and verify the active toolchain
with</span>
+rustup<span class="w"> </span>show
+
+<span class="c1"># 2. Install protoc 3.15+ (see details below)</span>
+protoc<span class="w"> </span>--version
+
+<span class="c1"># 3. Download test data used by examples and many tests</span>
+git<span class="w"> </span>submodule<span class="w"> </span>update<span
class="w"> </span>--init<span class="w"> </span>--recursive
+
+<span class="c1"># 4. Build the workspace</span>
+cargo<span class="w"> </span>build
+
+<span class="c1"># 5. Verify that Rust integration tests can be run</span>
+cargo<span class="w"> </span><span class="nb">test</span><span class="w">
</span>-p<span class="w"> </span>datafusion<span class="w"> </span>--test<span
class="w"> </span>parquet_integration
+
+<span class="c1"># 6. Verify that sqllogictests can run</span>
+cargo<span class="w"> </span><span class="nb">test</span><span class="w">
</span>--profile<span class="o">=</span>ci<span class="w"> </span>--test<span
class="w"> </span>sqllogictests
+</pre></div>
+</div>
+<p>Notes:</p>
+<ul class="simple">
+<li><p>The pinned Rust version is defined in <code class="docutils literal
notranslate"><span class="pre">rust-toolchain.toml</span></code>.</p></li>
+<li><p><code class="docutils literal notranslate"><span
class="pre">protoc</span></code> is required to compile DataFusion from
source.</p></li>
+<li><p>Some tests and examples rely on git submodule data being present
locally.</p></li>
+</ul>
+</section>
<section id="windows-setup">
-<h2>Windows setup<a class="headerlink" href="#windows-setup" title="Link to
this heading">#</a></h2>
+<h2>Windows Setup<a class="headerlink" href="#windows-setup" title="Link to
this heading">#</a></h2>
<div class="highlight-shell notranslate"><div
class="highlight"><pre><span></span>wget<span class="w">
</span>https://az792536.vo.msecnd.net/vms/VMBuild_20190311/VirtualBox/MSEdge/MSEdge.Win10.VirtualBox.zip
choco<span class="w"> </span>install<span class="w"> </span>-y<span class="w">
</span>git<span class="w"> </span>rustup.install<span class="w">
</span>visualcpp-build-tools
git-bash.exe
@@ -433,7 +463,7 @@ cargo<span class="w"> </span>build
<h2>Dev Container setup<a class="headerlink" href="#dev-container-setup"
title="Link to this heading">#</a></h2>
<p>DataFusion has support for <a class="reference external"
href="https://containers.dev/";>dev containers</a> which may be used for
developing DataFusion in an isolated environment either locally or remote if
desired. Using dev containers for developing
-DataFusion is not a requirement by any means but is available for those where
doing local development could be tricky
+DataFusion is not a requirement but is available where doing local development
could be tricky
such as with Windows and WSL2, those with older hardware, etc.</p>
<p>For specific details on IDE support for dev containers see the
documentation for <a class="reference external"
href="https://code.visualstudio.com/docs/devcontainers/containers";>Visual
Studio Code</a>,
<a class="reference external"
href="https://www.jetbrains.com/help/idea/connect-to-devcontainer.html";>IntelliJ
IDEA</a>,
@@ -441,9 +471,9 @@ such as with Windows and WSL2, those with older hardware,
etc.</p>
<a class="reference external"
href="https://docs.github.com/en/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers";>GitHub
Codespaces</a>.</p>
</section>
<section id="protoc-installation">
-<h2>Protoc Installation<a class="headerlink" href="#protoc-installation"
title="Link to this heading">#</a></h2>
+<h2><code class="docutils literal notranslate"><span
class="pre">protoc</span></code> Installation<a class="headerlink"
href="#protoc-installation" title="Link to this heading">#</a></h2>
<p>Compiling DataFusion from sources requires an installed version of the
protobuf compiler, <code class="docutils literal notranslate"><span
class="pre">protoc</span></code>.</p>
-<p>On most platforms this can be installed from your system’s package
manager</p>
+<p>On most platforms this can be installed from your system’s package manager.
For example:</p>
<div class="highlight-default notranslate"><div
class="highlight"><pre><span></span># Ubuntu
$ sudo apt install -y protobuf-compiler
@@ -465,7 +495,7 @@ libprotoc<span class="w"> </span><span
class="m">3</span>.15.0
<p>Alternatively a binary release can be downloaded from the <a
class="reference external"
href="https://github.com/protocolbuffers/protobuf/releases";>Release Page</a> or
<a class="reference external"
href="https://github.com/protocolbuffers/protobuf/blob/main/src/README.md";>built
from source</a>.</p>
</section>
<section id="bootstrap-environment">
-<h2>Bootstrap environment<a class="headerlink" href="#bootstrap-environment"
title="Link to this heading">#</a></h2>
+<h2>Bootstrap Environment<a class="headerlink" href="#bootstrap-environment"
title="Link to this heading">#</a></h2>
<p>DataFusion is written in Rust and it uses a standard rust toolkit:</p>
<ul class="simple">
<li><p><code class="docutils literal notranslate"><span
class="pre">rustup</span> <span class="pre">update</span> <span
class="pre">stable</span></code> DataFusion generally uses the latest stable
release of Rust, though it may lag when new Rust toolchains release</p>
@@ -545,10 +575,11 @@ libprotoc<span class="w"> </span><span
class="m">3</span>.15.0
</div>
<nav class="bd-toc-nav page-toc"
aria-labelledby="pst-page-navigation-heading-2">
<ul class="visible nav section-nav flex-column">
-<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#windows-setup">Windows setup</a></li>
+<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#quick-start">Quick Start</a></li>
+<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#windows-setup">Windows Setup</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#dev-container-setup">Dev Container setup</a></li>
-<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#protoc-installation">Protoc Installation</a></li>
-<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#bootstrap-environment">Bootstrap environment</a></li>
+<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#protoc-installation"><code class="docutils literal notranslate"><span
class="pre">protoc</span></code> Installation</a></li>
+<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#bootstrap-environment">Bootstrap Environment</a></li>
</ul>
</nav></div>
diff --git a/contributor-guide/index.html b/contributor-guide/index.html
index 16e32fe0b2..04780ecabb 100644
--- a/contributor-guide/index.html
+++ b/contributor-guide/index.html
@@ -431,8 +431,9 @@ members reviewing each other’s PRs. Doing so is a great way
to help the
community as well as get more familiar with Rust and the relevant
codebases.</p>
<section id="development-environment">
<h2>Development Environment<a class="headerlink"
href="#development-environment" title="Link to this heading">#</a></h2>
-<p>Setup your development environment <a class="reference internal"
href="development_environment.html"><span class="std std-doc">here</span></a>,
and learn
-how to test the code <a class="reference internal" href="testing.html"><span
class="std std-doc">here</span></a>.</p>
+<p>Start with the <a class="reference internal"
href="development_environment.html#quick-start"><span class="std
std-ref">Development Environment Quick Start</span></a>.</p>
+<p>For more detail, see the full <a class="reference internal"
href="development_environment.html"><span class="std std-doc">development
environment guide</span></a>
+and the <a class="reference internal" href="testing.html"><span class="std
std-doc">testing guide</span></a>.</p>
</section>
<section id="finding-and-creating-issues-to-work-on">
<h2>Finding and Creating Issues to Work On<a class="headerlink"
href="#finding-and-creating-issues-to-work-on" title="Link to this
heading">#</a></h2>
@@ -488,6 +489,17 @@ committer who approved your PR to help remind them to
merge it.</p>
<p>If you are concerned that a larger design will be lost in a string of small
PRs, creating a large draft PR that shows how they all work together can
help.</p>
<p>Note all commits in a PR are squashed when merged to the <code
class="docutils literal notranslate"><span class="pre">main</span></code>
branch so there is one commit per PR after merge.</p>
</section>
+<section id="before-submitting-a-pr">
+<h2>Before Submitting a PR<a class="headerlink" href="#before-submitting-a-pr"
title="Link to this heading">#</a></h2>
+<p>Before submitting a PR, run the standard non-functional checks. PRs must
pass
+before merge.</p>
+<div class="highlight-bash notranslate"><div
class="highlight"><pre><span></span>./dev/rust_lint.sh
+<span class="c1"># use `--write` to automatically fix some formatting and lint
errors</span>
+<span class="c1"># ./dev/rust_lint.sh --write --allow-dirty</span>
+</pre></div>
+</div>
+<p>You should also run any relevant commands from the <a class="reference
internal" href="testing.html#testing-quick-start"><span class="std
std-ref">testing quick start</span></a>.</p>
+</section>
<section id="conventional-commits-labeling-prs">
<h2>Conventional Commits & Labeling PRs<a class="headerlink"
href="#conventional-commits-labeling-prs" title="Link to this
heading">#</a></h2>
<p>We generate change logs for each release using an automated process that
will categorize PRs based on the title
@@ -658,6 +670,7 @@ Commenting on the PR will remove the <code class="docutils
literal notranslate">
<li class="toc-h1 nav-item toc-entry"><a class="reference internal nav-link"
href="#developer-s-guide">Developer’s guide</a><ul class="visible nav
section-nav flex-column">
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#pull-request-overview">Pull Request Overview</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#creating-pull-requests">Creating Pull Requests</a></li>
+<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#before-submitting-a-pr">Before Submitting a PR</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#conventional-commits-labeling-prs">Conventional Commits & Labeling
PRs</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#reviewing-pull-requests">Reviewing Pull Requests</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#performance-improvements">Performance Improvements</a></li>
diff --git a/contributor-guide/testing.html b/contributor-guide/testing.html
index 0f0c0a1dc9..1e6fcc2760 100644
--- a/contributor-guide/testing.html
+++ b/contributor-guide/testing.html
@@ -422,6 +422,30 @@
<p>Tests are critical to ensure that DataFusion is working properly and
is not accidentally broken during refactorings. All new features
should have test coverage and the entire test suite is run as part of CI.</p>
+<section id="testing-quick-start">
+<h2>Testing Quick Start<a class="headerlink" href="#testing-quick-start"
title="Link to this heading">#</a></h2>
+<p>While developing a feature or bug fix, best practice is to run the smallest
set
+of tests that gives confidence for your change, then expand as needed.</p>
+<p>Initially, run the tests in the crates you changed. For example, if you
made changes
+to files in <code class="docutils literal notranslate"><span
class="pre">datafusion-optimizer/src</span></code>, run the corresponding crate
tests:</p>
+<div class="highlight-shell notranslate"><div
class="highlight"><pre><span></span>cargo<span class="w"> </span><span
class="nb">test</span><span class="w"> </span>-p<span class="w">
</span>datafusion-optimizer
+</pre></div>
+</div>
+<p>Then, run the <code class="docutils literal notranslate"><span
class="pre">sqllogictest</span></code> suite, which provides a strong
speed–coverage tradeoff for development: it runs quickly while offering broad
regression coverage across most SQL behavior in DataFusion.</p>
+<div class="highlight-shell notranslate"><div
class="highlight"><pre><span></span>cargo<span class="w"> </span><span
class="nb">test</span><span class="w"> </span>--profile<span
class="o">=</span>ci<span class="w"> </span>--test<span class="w">
</span>sqllogictests
+</pre></div>
+</div>
+<p>Finally, before submitting a PR, run the tests for the core <code
class="docutils literal notranslate"><span class="pre">datafusion</span></code>
and
+<code class="docutils literal notranslate"><span
class="pre">datafusion-cli</span></code> crates:</p>
+<div class="highlight-shell notranslate"><div
class="highlight"><pre><span></span>cargo<span class="w"> </span><span
class="nb">test</span><span class="w"> </span>-p<span class="w">
</span>datafusion
+cargo<span class="w"> </span><span class="nb">test</span><span class="w">
</span>-p<span class="w"> </span>datafusion-cli
+</pre></div>
+</div>
+<p>Some integration tests require optional external services such as
Docker-backed
+containers and may skip when unavailable.</p>
+</section>
+<section id="testing-overview">
+<h2>Testing Overview<a class="headerlink" href="#testing-overview" title="Link
to this heading">#</a></h2>
<p>DataFusion has several levels of tests in its <a class="reference external"
href="https://martinfowler.com/articles/practical-test-pyramid.html";>Test
Pyramid</a> and tries to follow
the Rust standard <a class="reference external"
href="https://doc.rust-lang.org/book/ch11-03-test-organization.html";>Testing
Organization</a> described in <a class="reference external"
href="https://doc.rust-lang.org/book/";>The Book</a>.</p>
<p>Run tests using <code class="docutils literal notranslate"><span
class="pre">cargo</span></code>:</p>
@@ -432,6 +456,7 @@ the Rust standard <a class="reference external"
href="https://doc.rust-lang.org/
<div class="highlight-shell notranslate"><div
class="highlight"><pre><span></span>cargo<span class="w"> </span>nextest<span
class="w"> </span>run
</pre></div>
</div>
+</section>
<section id="unit-tests">
<h2>Unit tests<a class="headerlink" href="#unit-tests" title="Link to this
heading">#</a></h2>
<p>Tests for code in an individual module are defined in the same source file
with a <code class="docutils literal notranslate"><span
class="pre">test</span></code> module, following Rust convention.</p>
@@ -605,6 +630,8 @@ tested in the same way using the <a class="reference
external" href="https://doc
</div>
<nav class="bd-toc-nav page-toc"
aria-labelledby="pst-page-navigation-heading-2">
<ul class="visible nav section-nav flex-column">
+<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#testing-quick-start">Testing Quick Start</a></li>
+<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#testing-overview">Testing Overview</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#unit-tests">Unit tests</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#sqllogictests-tests">sqllogictests Tests</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link"
href="#snapshot-testing-cargo-insta">Snapshot testing (<code class="docutils
literal notranslate"><span class="pre">cargo</span> <span
class="pre">insta</span></code>)</a></li>
diff --git a/searchindex.js b/searchindex.js
index 867400db0c..707dbd465c 100644
--- a/searchindex.js
+++ b/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"alltitles":{"!=":[[72,"op-neq"]],"!~":[[72,"op-re-not-match"]],"!~*":[[72,"op-re-not-match-i"]],"!~~":[[72,"id19"]],"!~~*":[[72,"id20"]],"#":[[72,"op-bit-xor"]],"%":[[72,"op-modulo"]],"&":[[72,"op-bit-and"]],"(relation,
name) tuples in logical fields and logical columns are
unique":[[14,"relation-name-tuples-in-logical-fields-and-logical-columns-are-unique"]],"*":[[72,"op-multiply"]],"+":[[72,"op-plus"]],"-":[[72,"op-minus"]],"/":[[72,"op-divide"]],"1.
Array Literal Con [...]
\ No newline at end of file
+Search.setIndex({"alltitles":{"!=":[[72,"op-neq"]],"!~":[[72,"op-re-not-match"]],"!~*":[[72,"op-re-not-match-i"]],"!~~":[[72,"id19"]],"!~~*":[[72,"id20"]],"#":[[72,"op-bit-xor"]],"%":[[72,"op-modulo"]],"&":[[72,"op-bit-and"]],"(relation,
name) tuples in logical fields and logical columns are
unique":[[14,"relation-name-tuples-in-logical-fields-and-logical-columns-are-unique"]],"*":[[72,"op-multiply"]],"+":[[72,"op-plus"]],"-":[[72,"op-minus"]],"/":[[72,"op-divide"]],"1.
Array Literal Con [...]
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
