From 442ef6d1a538083fb17e18cf1d9d38c0990a9410 Mon Sep 17 00:00:00 2001 From: bendk Date: Tue, 14 Nov 2023 09:15:42 -0500 Subject: [PATCH] Update docs/adr/0009-async-rust.md Co-authored-by: Lina Butler --- docs/adr/0009-async-rust.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/adr/0009-async-rust.md b/docs/adr/0009-async-rust.md index 7297654073..f7f83d4610 100644 --- a/docs/adr/0009-async-rust.md +++ b/docs/adr/0009-async-rust.md @@ -10,7 +10,7 @@ Our Rust components are currently written using synchronous Rust. The components are then wrapped in Kotlin to present an async interface. Swift also wraps them to present an async-style interface, although it currently uses `DispatchQueue` and completion handlers rather than `async` functions. -UniFFI has been adding async capabilities in the last year and it seems possible to switch to using async Rust and not having an async wrapper. +UniFFI has been adding async capabilities in the last year and it seems possible to switch to using async Rust and not having a hand-written async wrapper. It also seems possible to auto-generate the async wrapper with UniFFI. What should our async strategy be?