a0b5e32f98
The Message struct had a reference to the context which made a few APIs a little easier. However it has surprising consequences a long way down the line as shown in #335: it means any object which has such a reference needs to keep open a lock if we want to do this refactor of no longer having a "closed" Context struct on the Rust API (which has many benefits which will simply that Context struct and is more the Rust way - RAII etc). By refactoring away the context reference on the rust API as done in here however, we push this behaviour of how these references are handled back to the C-API pointer behaviour: that is unsafe but just works in a C-like way. The resulting complexity in the FFI layer is also notably less than in the #335 alternative. As a consequence all APIs which require the context, now explicitly need to get the context passed in as an argument. It looks like this is certainly no downside and maybe even beneficial for further API refactors. For this strategy to work out the same should be done to dc_chatlist_t, dc_chat_t and dc_contact_t. But this working for dc_msg_t give a reasonable confidence that this is a good approach.
Delta Chat Rust
Project porting deltachat-core to rust
Current commit on deltachat/deltachat-core: 12ef73c8e76185f9b78e844ea673025f56a959ab.
Installing Rust and Cargo
To download and install the official compiler for the Rust programming language, and the Cargo package manager, run the command in your user environment:
curl https://sh.rustup.rs -sSf | sh
Using the CLI client
Compile and run Delta Chat Core using cargo:
cargo run --example repl -- /path/to/db
Configure your account (if not already configured):
Delta Chat Core is awaiting your commands.
> set addr your@email.org
> set mail_pw yourpassword
> configure
Connect to your mail server (if already configured):
> connect
Create a contact:
> addcontact yourfriends@email.org
Command executed successfully.
List contacts:
> listcontacts
Contact#10: <name unset> <yourfriends@email.org>
Contact#1: Me √√ <your@email.org>
Create a chat with your friend and send a message:
> createchat 10
Single#10 created successfully.
> chat 10
Single#10: yourfriends@email.org [yourfriends@email.org]
> send hi
Message sent.
If yourfriend@email.org uses DeltaChat, but does not receive message just
sent, it is advisable to check Spam folder. It is known that at least
gmx.com treat such test messages as spam, unless told otherwise with web
interface.
List messages when inside a chat:
> chat
For more commands type:
> help
Development
# run tests
$ cargo test --all
# build c-ffi
$ cargo build -p deltachat_ffi --release
Expensive tests
Some tests are expensive and marked with #[ignore], to run these
use the --ignored argument to the test binary (not to cargo itself):
$ cargo test -- --ignored
Features
vendored: When using Openssl for TLS, this bundles a vendored version.nightly: Enable nightly only performance and security related features.ringbuf: Enable the use ofslice_dequein pgp.