Migrate to Zig 0.14.1 #275
Merged
Conversation
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
|
Thanks! Could there please be a release? For example, Guix packages Zig packages and we (distributions) highly prefer tags over commits. |
Collaborator
Author
Yes will do now! |
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.
In my personal game, I'm up to a point where I'm working on the asset pipeline and I want to experiment using ZON instead of JSON as the structured text format. It looks like they won't be a new mach nominated Zig for a while so I decided to jump all my projects to Zig stable 0.14.1 until a newer mach nominated Zig is released.
I gonna leave this PR open for a day or 2 to let contributors readjust their setup and migrate to Zig 0.14.1