Array Returns | Callbacks | Globals | Struct Helpers

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

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

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

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

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

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

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()

SIMDe and native ISA compilation | Benchmarking backend switching

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

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

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

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