adjust as per Franck's comments

This commit is contained in:
Ivan Folgueira Bande 2025-07-29 09:28:39 +02:00
parent ebdaa0dfef
commit 3005c54a7e
No known key found for this signature in database
GPG Key ID: 3C117481F89E24A7
2 changed files with 8 additions and 8 deletions

View File

@ -3,13 +3,14 @@
## Functionality
1. Provides the core logic needed to expose any synchronous or asynchronous Nim library to a C-FFI library.
2. The exposed C library can be used in Golang.
3. The exposed C library can be used in Rust.
4. The exposed C library can be used in Python.
## Usability
1. Introduce new pragma definitions, such as `{.ffi.}`, to appropriately annotate types and procedures.
2. Any Nim project can use it and can be installed using Nimble,
similarly to how nim-chronos is imported.
3. The interaction with the exposed C library is through JSON.
4. The interaction with the exposed C library is through protobuf.
## Reliability
@ -22,10 +23,9 @@
## Supportability
1. Any Nim project can use it and can be installed using Nimble,
similarly to how nim-chronos is imported.
2. The interaction with the exposed C library is through JSON.
3. The interaction with the exposed C library is through protobuf.
1. The exposed C library can be used in Golang.
2. The exposed C library can be used in Rust.
3. The exposed C library can be used in Python.
## + (Privacy, Anonymity, Deployments)

View File

@ -85,7 +85,7 @@ This deliverable takes care of the following [Nim FFI](/FURPS/application/nim_ff
- F1.
- U1.
- S1.
- U2.
- +1. `nwaku` repository uses `nim-ffi` to expose the existing `libwaku` functionality.
**Checklist**: