Rust Version

[shps951023]

[shps951023]

Rust XLSX MVP implemented

The first Rust implementation has been merged into master in commit 8e5bec8.

Delivered

• A Rust 2024 workspace under rust/, with Rust 1.85.0 as the MSRV and a committed lockfile.
• An idiomatic miniexcel crate centered on XlsxReader<R> and XlsxWriter.
• XLSX reading from paths and Read + Seek sources, including worksheet listing/selection, ordered dynamic rows, Serde-based typed rows, A1 start cells, header handling, and optional empty-row filtering.
• New XLSX workbook creation from dynamic rows or Serde structs, including multiple worksheets and output to paths, byte buffers, or Write + Send targets.
• Dynamic and typed handling for strings, booleans, numbers, blanks, Excel errors, dates, times, datetimes, and durations.
• MiniExcel-compatible defaults where practical, with the differences documented explicitly.
• Runnable read/write examples, an English guide, a Simplified Chinese guide, and compatibility notes.
• A separate Rust CI workflow covering formatting, Clippy, rustdoc, Linux/Windows tests, and the Rust 1.85.0 MSRV.

The MVP uses calamine 0.35 for reading and rust_xlsxwriter 0.96 for writing. These versions were selected because their current successors require Rust 1.88.

Validation

• Rust 1.85.0 --locked --all-targets check passed.
• cargo fmt --check passed.
• Clippy passed with -D warnings.
• Rustdoc passed with -D warnings.
• 2 unit tests and 17 integration tests passed.
• Both read and write examples compiled and ran successfully.
• 54 related .NET OpenXML importer regression tests passed against the shared XLSX fixtures.

MVP boundaries

This version intentionally does not claim true streaming or async reading because calamine materializes worksheet ranges. Writing creates or overwrites new workbooks and cannot modify existing files. CSV, legacy Excel formats, templates, formula authoring, images, merged-cell APIs, arbitrary range-end coordinates, general styling, WASM, and crates.io publication remain deferred for later milestones.

[michelebastione]

@shps951023 I think this implementation should go in its own repository, or at the very least in a separate branch. My opinion is that it would be difficult and potentially confusing to keep the both of them together when their respective toolchains and ecosystems have nothing in common.

[shps951023]

@michelebastione Good day, I will create a new project miniexcel-rust https://github.com/mini-software/MiniExcel-Rust 🙌