feat(topolotree): new implementation and Hydro Deploy setup

.github/workflows/build-cli.yml

@@ -105,17 +105,8 @@ jobs:
         with:
           working-directory: hydro_cli
           target: ${{ matrix.platform.target }}
-          manylinux: musllinux_1_2
+          manylinux: auto
           args: --release --out dist
-      - uses: uraimo/run-on-arch-action@master
-        name: Install built wheel
-        with:
-          arch: ${{ matrix.platform.arch }}
-          distro: alpine_latest
-          install: |
-            apk add py3-pip
-          run: |
-            pip3 install ${{ env.PACKAGE_NAME }} --no-index --find-links hydro_cli/dist/ --force-reinstall
       - name: "Upload wheels"
         uses: actions/upload-artifact@v3
         with:

.github/workflows/ci.yml

@@ -56,7 +56,7 @@ jobs:
         uses: actions-rs/cargo@v1
         with:
           command: check
-          args: --all-targets
+          args: --all-targets --features python
 
   check-wasm:
     name: Check WebAssembly
@@ -91,7 +91,7 @@ jobs:
         uses: actions-rs/cargo@v1
         with:
           command: check
-          args: -p hydroflow_lang --target wasm32-unknown-unknown --no-default-features
+          args: -p hydroflow_lang --target wasm32-unknown-unknown
 
   test:
     name: Test Suite
@@ -121,11 +121,17 @@ jobs:
           toolchain: nightly
           override: ${{ matrix.rust_release == 'latest-nightly' }}
 
-      - name: Run cargo test
+      - name: Run cargo test all targets (which does not include doctests)
+        uses: actions-rs/cargo@v1
+        with:
+          command: test
+          args: --no-fail-fast --all-targets --features python
+
+      - name: Run cargo doc tests
         uses: actions-rs/cargo@v1
         with:
           command: test
-          args: --no-fail-fast
+          args: --no-fail-fast --doc --features python
 
   test-wasm:
     name: Test Suite (WebAssembly)
@@ -275,7 +281,21 @@ jobs:
         uses: actions-rs/cargo@v1
         with:
           command: clippy
-          args: --all-targets -- -D warnings
+          args: --all-targets --features python -- -D warnings
+
+  build-website:
+    name: Build Website
+    if: ${{ needs.pre_job.outputs.should_skip != 'true' || github.event_name != 'pull_request' }}
+    timeout-minutes: 25
+    needs: pre_job
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout sources
+        uses: actions/checkout@v3
+
+      - name: Build Website
+        run: bash build_docs.bash x86_64-linux-gnu-ubuntu-20.04
 
   docs:
     name: Docs (rustdoc)

Cargo.toml

@@ -22,6 +22,7 @@ members = [
     "multiplatform_test",
     "pusherator",
     "relalg",
+    "topolotree",
     "variadics",
     "website_playground",
 ]

README.md

@@ -7,8 +7,8 @@
     <a href="https://docs.rs/hydroflow/"><img src="https://img.shields.io/badge/docs.rs-Hydroflow-blue?style=flat-square&logo=read-the-docs&logoColor=white" alt="Docs.rs"></a>
 </p>
 
-Hydroflow is a low-latency dataflow runtime written in Rust. The [Hydro Project](https://hydro.run/docs/hydroflow/ecosystem/)
-will empower developers to harness the full potential of the cloud by making distributed programs easy to specify and automatic to scale. Hydroflow serves as the lowest level in the [Hydro stack](https://hydro.run/docs/hydroflow/ecosystem/),
+Hydroflow is a low-latency dataflow runtime written in Rust. The goal of the [Hydro Project](https://hydro.run)
+is to empower developers to harness the full potential of the cloud by making distributed programs easy to specify and automatic to scale. Hydroflow is the lowest level in the [Hydro stack](https://hydro.run/docs/hydroflow/ecosystem/),
 serving as a single-node low-latency runtime with explicit networking. This allows us to support
 not just data processing pipelines, but distributed protocols (e.g. Paxos) and real-world
 long-running applications as well.
@@ -17,16 +17,16 @@ Take a look at the [Hydroflow Book](https://hydro.run/docs/hydroflow/).
 
 ## The Hydroflow Surface Syntax
 
-Hydroflow comes with a custom "surface syntax" domain-specific language which serves as a very
-simple, readable IR for specifying single-node Hydroflow programs, intended to be stitched together
-by the Hydro stack to create larger autoscaling distributed systems.'
+Hydroflow comes with a custom "surface syntax"—a domain-specific language which serves as a very
+simple, readable IR for specifying single-node Hydroflow programs. These programs are intended to be stitched together
+by the Hydro stack to create larger autoscaling distributed systems.
 
 Here's a simple example of the surface syntax. Check out the [Hydroflow Playground](https://hydro.run/playground)
 for an interactive demo.
 ```rust
 source_iter(0..10)
   -> map(|n| n * n)
-  -> filter(|&n| n > 10)
+  -> filter(|n| *n > 10)
   -> foo;
 
 foo = map(|n| (n..=n+1))

benches/benches/fork_join.rs

@@ -54,11 +54,7 @@ fn benchmark_hydroflow(c: &mut Criterion) {
                     send1,
                     send2,
                     |_ctx, recv1, recv2, send1, send2| {
-                        for v in recv1
-                            .take_inner()
-                            .into_iter()
-                            .chain(recv2.take_inner().into_iter())
-                        {
+                        for v in recv1.take_inner().into_iter().chain(recv2.take_inner()) {
                             if v % 2 == 0 {
                                 send1.give(Some(v));
                             } else {