08801ab580
The Rust API has so far grown somewhat organically driven by the needs of the javascript implementation. This has led to an API which is quite awkward and unfamiliar to Rust programmers. Additionally there is no documentation to speak of. This commit is the first movement towards cleaning things up a bit. We touch a lot of files but the changes are all very mechanical. We introduce a few traits to abstract over the common operations between `Automerge` and `AutoCommit`, and add a whole bunch of documentation. * Add a `ReadDoc` trait to describe methods which read value from a document. make `Transactable` extend `ReadDoc` * Add a `SyncDoc` trait to describe methods necessary for synchronizing documents. * Put the `SyncDoc` implementation for `AutoCommit` behind `AutoCommit::sync` to ensure that any open transactions are closed before taking part in the sync protocol * Split `OpObserver` into two traits: `OpObserver` + `BranchableObserver`. `BranchableObserver` captures the methods which are only needed for observing transactions. * Add a whole bunch of documentation. The main changes Rust users will need to make is: * Import the `ReadDoc` trait wherever you are using the methods which have been moved to it. Optionally change concrete paramters on functions to `ReadDoc` constraints. * Likewise import the `SyncDoc` trait wherever you are doing synchronisation work * If you are using the `AutoCommit::*_sync_message` methods you will need to add a call to `AutoCommit::sync()` first. E.g. `doc.generate_sync_message` becomes `doc.sync().generate_sync_message` * If you have an implementation of `OpObserver` which you are using in an `AutoCommit` then split it into an implementation of `OpObserver` and `BranchableObserver` |
||
|---|---|---|
| .. | ||
| benches | ||
| src | ||
| .gitignore | ||
| automerge-1.0.js | ||
| automerge-js.js | ||
| automerge-wasm.js | ||
| baseline.js | ||
| Cargo.toml | ||
| editing-trace.js | ||
| edits.json | ||
| Makefile | ||
| package.json | ||
| README.md | ||
Edit trace benchmarks
Try the different editing traces on different automerge implementations
Automerge Experiement - pure rust
make rust
Benchmarks
There are some criterion benchmarks in the benches folder which can be run with cargo bench or cargo criterion.
For flamegraphing, cargo flamegraph --bench main -- --bench "save" # or "load" or "replay" or nothing can be useful.
Automerge Experiement - wasm api
make wasm
Automerge Experiment - JS wrapper
make js
Automerge 1.0 pure javascript - new fast backend
This assumes automerge has been checked out in a directory along side this repo
node automerge-1.0.js
Automerge 1.0 with rust backend
This assumes automerge has been checked out in a directory along side this repo
node automerge-rs.js
Baseline Test. Javascript Array with no CRDT info
make baseline