Conversation
7c71bda to
45daae4
Compare
There was a problem hiding this comment.
This lib actively uses protobuf, while C# client - doesn't.
So I see two variants there
- We will be having 2 FFI interfaces
- Rework golang bindings to avoid using protobuf
There was a problem hiding this comment.
Need to clean up some code comments which refer to golang
There was a problem hiding this comment.
- If 2 isn't possible, put protobuf functions under a feature flag. Please do it in the C# implementation.
| working-directory: ffi | ||
| run: | | ||
| cargo build --release | ||
| - name: Generate the C header file |
There was a problem hiding this comment.
It is needed for go client only and does not test the code
There was a problem hiding this comment.
it isn't go-specific, it can be used in other FFI wrappers as well (C++ for example)
Signed-off-by: barshaul <barshaul@amazon.com>
Signed-off-by: barshaul <barshaul@amazon.com>
Signed-off-by: barshaul <barshaul@amazon.com>
|
Sorry I missed reviewing this PR. Only comment I have is: I made the decision to compile to |
…key-io#3372) * Go/Core Refactore: Move FFI to a dedicated folder to be reusable for other wrappers Signed-off-by: barshaul <barshaul@amazon.com>
* Go/Core Refactore: Move FFI to a dedicated folder to be reusable for other wrappers Signed-off-by: barshaul <barshaul@amazon.com>
This PR relocates the FFI interface from the Go folder to a dedicated ffi folder, making it reusable for other language wrappers.
Currently, the FFI C-Rust implementation is located under the Go folder since it has only been used for Go. However, as we expand support for additional wrappers, such as the C# and Python Sync clients, which will communicate via FFI instead of UDS, we need to move the logic out of the Go folder to improve reusability and maintainability.
Issue link
This Pull Request is linked to issue (URL): #3373
Checklist
Before submitting the PR make sure the following are checked: