Supported transports | Select the plan before registration | Worker-process (ipc) plan | Inspect workers | What rducks_release() does

Source and installed layout | Package and extension split | Runtime scopes | R-thread discipline | Scalar UDF registration and execution | Aggregates | Table functions | Query streams | IPC provider lifecycle | Ownership and copying model

Why Rducks ships exact-version extensions | Runtime selection | Unsupported versions | Maintainer workflow

Enable Rducks | Register a scalar UDF | Register an aggregate | Register a table function | Stream query results back to R | Release connection-local state

Submit and wait | Poll or race | Coordinating several handles with condition variables

A small explicit format layer | Add an explicit cache

S3-compatible examples | Google Drive | Azure Blob / GCS helpers

Root-relative paths | Range-heavy readers | Zarr-like byte stores | Control knobs belong in handles | Error values are first-class

Aio pattern with the same API

Write an object and an index | Read selected records by range | Async and byte handles

Dataflow | Async and thread safety | Serialization and codecs pipeline | Layer controls | API boundaries by function family

Async-first surface | Usage from another R package | Minimal usage pattern | Prefix-scoped byte stores | Why this exists

Raw and text modes | Serializers for R objects | Native codecs

Build a tiny alignment batch | The downstream C consumer | Compile and call it with Rtinycc

Boundary | Backends | R surface | Validation

Pin file | Patch queue | Developer checkout | Vendored source

1. HTTP Client | ncurl: Basic Requests | ncurl_aio: Async Requests | Promises Integration | ncurl_session: Persistent Connections | 2. WebSocket Client | 3. Unified HTTP/WebSocket Server | Handler Types | HTTP Request Handlers | Static Content Handlers | WebSocket Handlers | HTTP Streaming Handlers | Server-Sent Events | 4. Secure Connections (TLS) | Public Internet HTTPS | Self-Signed Certificates | 5. Client Example: Shiny ExtendedTask | 6. Server Example: Quarto Site with Dynamic API

1. Request Reply Protocol | 2. Publisher Subscriber Protocol | 3. Surveyor Respondent Protocol | 4. Device (Broker / Proxy)

Build a tiny alignment batch | The downstream C consumer | Compile and call it with Rtinycc

Pin file | Patch queue | Developer checkout | Vendored source

Boundary | Backends | R surface | Validation

Setup | Why a bridge is needed | Register selected R helpers for duckplyr | Why scalar mode is the default | Execution plans: in-process and worker-process | Cleanup

Function kind, scalar-UDF mode, and execution plan | Declared descriptors | NULL handling | Error handling and side effects | Runtime reference tables

Async-first surface | Usage from another R package | Minimal usage pattern | Prefix-scoped byte stores | Why this exists

Running Lean | Asserting the axiom base | Expected errors | Why this matters

A small explicit format layer | Add an explicit cache

Write an object and an index | Read selected records by range | Async and byte handles

Root-relative paths | Range-heavy readers | Zarr-like byte stores | Control knobs belong in handles | Error values are first-class

Scalar Inputs Are Converted | Vector Inputs Are Usually Borrowed | tcc_call_symbol() Uses .C()-Style Copy-In/Copy-Out | cstring_array Is Rebuilt Per Call | Returned Arrays Are Copied into Fresh R Vectors | Returned cstring Values Are Copied | Returned ptr Values Stay as Pointers | sexp Passes Through Directly | Owned vs Borrowed Helper Pointers | Bitfields Are Scalar Helpers, Not Addressable Views | Serialization Boundary

Submit and wait | Poll or race | Coordinating several handles with condition variables

S3-compatible examples | Google Drive | Azure Blob / GCS helpers

Aio pattern with the same API

Raw and text modes | Serializers for R objects | Native codecs

Dataflow | Async and thread safety | Serialization and codecs pipeline | Layer controls | API boundaries by function family

Copy the scaffold | Replace the demo kernels | Extending the number of operations | Build

Functions | Coordinates | Inputs | Match regions | Search strategies

Searching a batch | Qualities | Gzip input | Performance model | Validation story

Vendoring | Development commands | R build hooks

Install | Search | Reuse a searcher | Multiple patterns or texts | FASTA/FASTQ batches

SIMDe and native ISA compilation | Benchmarking backend switching

Auto selection | Explicit selection | Why separate backend libraries?

Three Minimal Cases | Availability | Compilation Latency | Generated Wrapper Code | noop() Call Overhead | fill_rand(out, n) And Zero-Copy Arrays | rand_unif(n) And Copy Cost | What These Numbers Mean

The tcc_ffi Object Is a Recipe | Code Generation Is Central | How Values Move Between R, The Wrapper, And C | Copying Versus Borrowing Happens In The Wrapper | Why lambda.r Is Used | Wrapper Builders Work at the SEXP Boundary | Protection And Lifetime Rules Matter | Ownership And Lifetime Semantics In The Main Cases | Call-scoped borrows from R objects | Owned native allocations | Borrowed native views | Returned R objects | Callback registry lifetime | Compiled object lifetime | Host Symbol Injection Happens Before Relocation | Callback Round-Trips Cross The Boundary Twice | State Creation Is Separate from Compilation | The Compiled Object Is an Environment of Closures | Serialization Works by Recompiling the Recipe | Where To Read Next

Introduction | Background | A structural interface | When the whole protocol is a class family | Progressive argument and return checks | Number-like behavior | Vector-like behavior | An explicit trait | A Haskell-style dictionary object | Which feels more natural? | References

Introduction | Background | A toy assay container | Operations and a consumer-owned interface | When an explicit trait helps | Design cautions | References

What tcc_link() Is For | A Minimal Linking Example | Adding Helper Code Beside External Symbols | Linking by Name or by Path | Relationship to tcc_compile()

Scalar Types | A Minimal Example | String and Pointer Types | Array Types | Direct R Objects with sexp

Array Returns | Callbacks | Globals | Struct Helpers

Allocation and Ownership | Reading and Writing Raw Bytes | Typed Reads and Writes | Pointer-to-Pointer Helpers | C String Helpers

Working with Struct Helpers | Registering Callbacks | Async Callback Caveats | Soundness Notes

Toolchain Paths | A Minimal FFI Example | Managing Globals | When to Use tcc_link()

Availability | Start from a Header Snippet | Inspect Parsed Functions | Generate a Working FFI Object | Struct Helpers | Conservative Type Mapping

Core Concepts | Key Takeaways | 1. Sockets and Connections | Create Sockets | Protocols | Transports | 2. Send and Receive | Synchronous | Receive Modes | 3. Async I/O | Basic Async | Non-blocking Patterns | 4. Condition Variables | Basics | Pipe Notifications | Async with CV | 5. Request/Reply (RPC) | Server | Client | 6. Pub/Sub | 7. Surveyor/Respondent | 8. TLS Secure Connections | Self-signed Certificates | CA Certificates | 9. Options and Statistics | Get/Set Options | Common Options | Custom Serialization | Statistics | 10. Contexts | 11. Cross-language Exchange | R to Python (NumPy) | 12. Error Handling | 13. Utilities

1. TLS Secure Connections | 2. Options | 3. Custom Serialization | 4. Statistics

1. Cross-language Exchange | 2. Async and Concurrency | 3. Synchronisation Primitives