clients/zig: add zig support (0.10.1) #74
Conversation
This file contains 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
The implementation is far from perfect, but I am tired of polishing it over the current state of Zig runtime. Probably, it will require an update after release of 0.11.0. Signed-off-by: Ivan Prisyazhnyy <john.koepi@gmail.com>
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.
If you wish, this is a working implementation of the Maelstrom node framework on Zig 0.10.1. There were many bugs I faced during this experiment. For example, async-io did not work. There are probably bugs with the memory control, but the examples work well.
The implementation is far from perfect, but I am tired of polishing it over the current state of Zig runtime. Probably, it will require an update after the release of 0.11.0. If anyone is interested in polishing look into many FIXME comments in the code.
One of the improvements could be an extension of the types of errors the Handlers can handle so that the
catchblocks disappear and allow the implementers to rely solely ontrycalls, but I don't have time at the moment to work on that.