You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible to use this with zig 0.13? I have tried zig fetch --save with the latest commit, and an older commit that mentions 0.13. Is there a particular commit for people not using the unstable zig?
I've tried these, and they both produce errors I don't know how to interpret
I'm not sur this is the last one compatible, but in view of log, I've checkout on this commit id ae5ecc1522da983dc39bb0d8b27f5d1b1d7956e3 to be compatible with zig 0.13.
That commit had failing tests so I was a bit weary of using it, and tried the one after it. It would be neat if this project had a tag or branch for 0.13. I know 0.14 is out soon, but it might take a while for all my project dependencies to catch up.
Hi there! "Historically", we are pinned on zig master until the language stabilizes, although it's a good idea to tag a version during zig milestones, I'll keep that in mind when 0.14 is released.
Is it possible to use this with zig 0.13? I have tried
zig fetch --save
with the latest commit, and an older commit that mentions 0.13. Is there a particular commit for people not using the unstable zig?I've tried these, and they both produce errors I don't know how to interpret
The text was updated successfully, but these errors were encountered: