-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zig tracking issue #58
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a tracking issue for upstream Zig. (see Third Party Tracking Issues)
Overall, Zig is really great and its cross-compilation abilities are great for GUIs, but some (planned) proposals and bug fixes would make it better:
capy.http
which has an async-looking API but is actually synchronous andcapy.assets
which is entirely synchronous as of now, including when fetching resources over HTTP.fn buttonClicked(button: *capy.Button) !void
instead of a more genericfn buttonClicked(button: *anyopaque) !void
. Having to manually@ptrCast
decreases the ease of use of the API.Atom.dependOn
instead of using the bizarre status quo ofstruct { fn a() void {} }.a
The text was updated successfully, but these errors were encountered: