31–40 of 80 posts
I'm curious about the tools zig offers around doing asyc work while guaranteeing certain invariants, and how the @Frame builtins work with that, but I'm guessing that's going to be elaborated on in a future post.
It's an exciting week for programming languages. First Nim, then Zig. Keep up the great work!
Does anyone here have a good understanding of the relative merits of Zig, Crystal, and Nim? Especially compared to higher profile languages like Rust and Go? All of these languages seem to be statically compiled, and they all seem to promise both performance and safety. Rust and Go are discussed all the time on HN, so I expect most of us here have a reasonable notion of their relative benefits, for example, performan…
https://ziglang.org/documentation/master/#Zen >> Minimize energy spent on coding style. For me this is sort of important because languages not having standard coding style end up 10000 coding styles. Rust fmt is an excellent example for avoiding that. Does anybody use Zig + fmt? I know they have something. https://github.com/ziglang/zig/issues/1523
There's a section in this notes about it https://ziglang.org/download/0.5.0/release-notes.html#zig-fm... The end even has a link to a web-based version of it.
Earlier quoted context omitted.
Can you give examples of the peculiarities? I write cpp all day and zig is a nice change for me because of how simple it is to me
> Zig both signed and unsigned integers have undefined behavior on overflow, contrasted to only signed integers in C make a feature unwanted in C, worse. nice.
In other words, the compiler will enforce that `a + b` does not overflow through all your testing and wherever you explicitly say such checks are required, but turns them into nops for you when you desire speed. You can let the compiler know that you explicitly want wrapping overflow (and not some undefined kind) using the wrapping operator `a +% b`.
Earlier quoted context omitted.
Can you give examples of the peculiarities? I write cpp all day and zig is a nice change for me because of how simple it is to me
> Zig both signed and unsigned integers have undefined behavior on overflow, contrasted to only signed integers in C make a feature unwanted in C, worse. nice.
Earlier quoted context omitted.
It's an unwillingness to implement documentation generation twice. Why do it in the c++ compiler when the goal is to become self-hosted? I think there's a good answer to this which is, "because people really, really need documentation." So I am kicking around ideas of how this can be done without too much duplicate effort.
I see. Do you think there would be value in having someone just manually writing some interim docs (perhaps as a wiki) until the time when it can be properly generated? This may seem like a weird place to draw experience from, but in my early days of programming, I've found the PHP docs extremely helpful largely thanks to community comments sections giving examples of how to do various things. Just some food for thou…
One of the tenets of my development process with Zig is "avoid local maximums". A wiki for std lib documentation is not the long term solution to the problem, and so I won't be investing any time into it. All my time is invested in the long term solution.
Earlier quoted context omitted.
You can use any c libraries networking or socket implementations in zig but I think thats as far as it goes at the moment.
zig's C-interoperability is second to none and using libcurl works great for networking. example: https://github.com/donpdonp/zootdeck/blob/master/src/net.zig
Earlier quoted context omitted.
You can use any c libraries networking or socket implementations in zig but I think thats as far as it goes at the moment.
zig's C-interoperability is second to none and using libcurl works great for networking. example: https://github.com/donpdonp/zootdeck/blob/master/src/net.zig