Conversation
Signed-off-by: inge4pres <fgualazzi@gmail.com>
Signed-off-by: inge4pres <fgualazzi@gmail.com>
Signed-off-by: inge4pres <fgualazzi@gmail.com>
Signed-off-by: inge4pres <fgualazzi@gmail.com>
Signed-off-by: inge4pres <fgualazzi@gmail.com>
Collaborator
Author
|
Proud to have accomplished this |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reason for this PR
Create C exports, statically linked library and relevant header file to allow C programs to consume the Zig implementation of the SDK.
Closes #56.
Details
Exposing Zig code to C was not as easy as I thought 😅
There are several limitations that I encountered and I had not foreseen simply due to my lack of experience on the matter (Dunning-Krueger?).
Nevertheless, the PR:
c.zigzig buildexample-c)Additional context
We should be more explicit that the C API is not going to be stable even when we stabilize the SDK.
The reason is: depending on the type of modifications we apply to the Zig SDK code, we might not reflect them immediately to the C code (it might require additional changes in the C part).
We cannot require contributors that changes to the Zig code are updated on the C part in the same PR, hence we are not going to flag the C API as stable.