Things Zig comptime won't do
matklad.github.io
Things Zig comptime won't do
1–10 of 252 posts
Re: Things Zig comptime won't do
#2Re: Things Zig comptime won't do
#3At some point you realize you need type information, so you just add it to your func params.
That bubbles all the way up and you are done. Or you realize in certain situation it is not possible to provide the type and you need to solve a arch/design issue.
Re: Things Zig comptime won't do
#4Perhaps the safety is the tradeoff with the comparative ease of using the language compared to Rust, but I’d love the best of both worlds if it were possible
Re: Things Zig comptime won't do
#5Re: Things Zig comptime won't do
#6Re: Things Zig comptime won't do
#7I like the Zig language and tooling. I do wish there was a safety mode that give the same guarantees as Rust, but it’s a huge step above C/C++. I am also extremely impressed with the Zig compiler. Perhaps the safety is the tradeoff with the comparative ease of using the language compared to Rust, but I’d love the best of both worlds if it were possible
TypeScript is to JavaScript
as
Zig is to C
I am a huge TS fan.
Re: Things Zig comptime won't do
#8Re: Things Zig comptime won't do
#9I'm curious what are these other languages that can do these things? I read HN regularly but don't recall them. Or maybe that's including things like Java's annotation processing which is so clunky that I wouldn't classify them to be equivalent.
Re: Things Zig comptime won't do
#10> Zig’s comptime feature is most famous for what it can do: generics!, conditional compilation!, subtyping!, serialization!, ORM! That’s fascinating, but, to be fair, there’s a bunch of languages with quite powerful compile time evaluation capabilities that can do equivalent things. I'm curious what are these other languages that can do these things? I read HN regularly but don't recall them. Or maybe that's includin…