Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
excelreader (Rust)
Read and write Excel/CSV workbooks via ExcelReader's native ABI: opening a workbook (from a path or memory, with the full open-options surface), sheet navigation, schema inference, schema-driven typed parse, and schema-driven writing. No Arrow, no row-by-row decode yet - see the root README's Python section for what those look like.
Usage
[]
= "2.1"
use ;
let mut workbook = open?;
let table = ?;
for row in table.iter
parse_sheet takes &mut Workbook because it consumes the workbook's shared row cursor.
Field types
| Field type | Column |
|---|---|
String |
XL_T_STRING |
i8..i64, isize, u8..u64, usize |
XL_T_I64 |
f32, f64 |
XL_T_F64 |
bool |
XL_T_BOOL |
Date / chrono::NaiveDate |
XL_T_DATE |
Time / chrono::NaiveTime |
XL_T_TIME |
Timestamp / chrono::NaiveDateTime |
XL_T_TIMESTAMP |
Option<T> of any of the above makes the field None when the cell is null; a non-Option field is
left at its Default instead.
Narrower integers convert through TryFrom and panic on a value that does not fit, rather than
wrapping silently. Date/Time/Timestamp are dependency-free newtypes over the exact wire
representation; enable the chrono feature to use chrono's calendar types directly:
= { = "2.1", = ["chrono"] }
Sheets and schema inference
let mut workbook = open?;
for in workbook.sheet_names?.iter.enumerate
workbook.move_to_sheet?;
// Guess a schema from the header row plus a sample of the data, before committing to one.
for column in workbook.infer_schema?
Workbook::open_with takes an explicit format and OpenOptions; Workbook::open_memory reads from
a byte slice. Note that format sniffing does not detect CSV - pass XL_FORMAT_CSV explicitly.
Arrow export (arrow feature)
= { = "2.1", = ["arrow"] }
use parse_arrow;
use Workbook;
let mut workbook = open?;
let batch = ?;
println!;
Off by default — arrow-rs is a large dependency and the typed-parse path needs none of it.
Writing
#[derive(ExcelMapper)] generates both halves, so the same struct reads and writes - the field
types in the table above apply unchanged:
use write_sheet;
use XL_FORMAT_XLSX;
write_sheet?;
Option<T> fields become an LSB-first validity bitmap: None writes a blank cell rather than a
zero. Only the primary #[excel(name = "...")] reaches the header - the alias list exists to
resolve a header on the way in, and the ABI rejects a write column carrying more than one name.
For buffers that are already columnar, write_columns borrows them and copies nothing. The
lifetimes on Column<'a> are what turn the ABI's borrow contract into something the compiler
checks:
use ;
use XL_FORMAT_XLSX;
let ids = ;
let columns = ;
write_columns?;
validity is checked against the row count before the call: the ABI takes the bitmap without a
length and reads (rows + 7) / 8 bytes on trust, so a short slice would be a buffer overrun rather
than a wrong answer.
WriteOptions sets the sheet name, the CSV dialect, and the XLS/XLSB and XLSX/XLSB toggles.
format_from_path infers the format from an extension; it returns XL_FORMAT_AUTO for anything it
does not recognize, which the write then rejects - a file being created has no signature bytes to
sniff, so there is nothing to fall back on.
write_sheet walks the slice once and appends each field to its own buffer, monomorphized per
field. That transpose is the only copy it makes; write_columns pays nothing.
Streaming writes
write_sheet/write_columns build the whole table in memory first. writer_handle::WriterHandle is
the row-by-row alternative, writing directly as each call arrives instead:
use WriterHandle;
let mut handle = open?;
handle.start_sheet?;
handle.start_row?;
handle.write_str?;
handle.write_i64?;
handle.end_row?;
handle.end_sheet?;
Call order mirrors the C ABI's xl_writer_handle: open/open_with/open_memory, then per sheet
start_sheet..end_sheet, each containing start_row..end_row with one write_* call per cell
(None writes a blank cell), left to right. A call out of order returns Err rather than
corrupting output. open_memory backs the handle with an in-memory buffer instead of a file; read
it out with bytes(). Dropping a WriterHandle closes and releases it, same as Workbook — call
bytes() (memory-backed) or reopen the path (file-backed) to observe the result rather than relying
on the drop for that.
Bounds and panics
TableView::get returns Option<T> and is None outside 0..len(). The column_* accessors used
by generated bindings panic on an out-of-range row, a column type that does not match the binding, or
a string the native library returned as non-UTF-8 - each is a contract violation rather than
recoverable input.
Build notes
build.rs downloads the native ExcelReader.Native binary matching your target from the crate's
matching GitHub Release. Set EXCELREADER_NATIVE_LIB_DIR to a directory containing a locally-built
copy instead (e.g. from dotnet publish ../../src/ExcelReader.Native -r win-x64) to skip that
download - useful when building from source before a release exists yet.
Every constructor first checks the loaded library's xl_abi_version() against the XL_ABI_VERSION
this crate was compiled against, and fails with a explanatory error rather than reading native memory
through a layout that may have changed.
Benchmarks
Criterion suite in benches/. Measured on Windows 10 (22H2), 16 logical CPUs @ 3.39 GHz,
rustc 1.97.1 (Release), Criterion 0.5, 100 samples per benchmark (medians shown). write_bench
takes 20 samples instead — each of its iterations writes a whole 65,535-row file.
benches/parse_bench.rs - open/parse_sheet/infer_schema, same methodology as the C++ suite:
| Benchmark | RealExcel.xlsb (100 rows) | 65K_Records_Data.xlsb (65,535 rows) |
|---|---|---|
open |
79.4 µs | 92.8 µs |
parse_sheet (2 or 6 bound columns) |
79.0 µs | 39.3 ms |
infer_schema (sample 100 / 1,000 rows) |
147.9 µs | 1.19 ms |
open stays nearly flat across the 655x row-count jump (+17%) - XLSB's header carries its
dimensions/index, so opening costs metadata, not row data. parse_sheet scales linearly with
rows × columns; infer_schema scales with its sample size, not the file's total row count.
benches/compare_bench.rs compares against calamine reading
65K_Records_Data.{xlsx,xlsb} in full (all 14 columns, 65,535 rows). Both sides decode every cell
into an owned value (String for text) and fold it into one accumulator, so neither side gets a
zero-copy advantage the other can't take:
| Format | ExcelReader (parse_sheet::<FullRow>) |
calamine (worksheet_range + Data match) |
|---|---|---|
| XLSX | 123.5 ms | 273.4 ms |
| XLSB | 70.6 ms | 84.9 ms |
ExcelReader is ~2.2x faster than calamine for XLSX and ~1.2x faster for XLSB on this workload - calamine is a fast, well-optimized reader in its own right, so the gap is real but not the order of magnitude seen against slower libraries.
benches/write_bench.rs measures the two write layers and
rust_xlsxwriter writing the same 7 columns × 65,535
rows to .xlsx, all three starting from the same in-memory Vec<Row>:
| Benchmark | Median |
|---|---|
columns (write_columns, pre-transposed) |
62.1 ms |
sheet (write_sheet, from Vec<Row>) |
67.2 ms |
rust_xlsxwriter (cell-at-a-time) |
336.9 ms |
sheet is the matched-work number — it starts from the same shape rust_xlsxwriter is handed and
pays the row-to-column transpose itself — and is ~5.0x faster. columns is a ceiling no
cell-at-a-time API can reach, since it is handed buffers that are already columnar; read it only
against sheet, as the cost of having row-shaped data in the first place. That cost turns out to be
about 8%: the transpose is nearly free next to producing the file.
Two caveats, both running against the headline number rather than for it. ExcelReader does slightly
more work here: it attaches a number format to the date column so Excel shows a date, and writes a
header row, while the rust_xlsxwriter case writes that column as a bare serial number and no
header. And rust_xlsxwriter carries formatting and formula support this library does not expose at
all, so its number reflects a different feature set, not only a slower path.
Run locally:
EXCELREADER_NATIVE_LIB_DIR=/path/to/native/lib/dir
EXCELREADER_NATIVE_LIB_DIR should point at a directory containing a locally-built
ExcelReader.Native.{dll,so,dylib} - see Build notes above. Pass
--bench parse_bench, --bench compare_bench or --bench write_bench to run one suite only.