Of course compiling something without checks is safe. If that’s your standard, we should write the kernel in JS, Python, Ruby, LUA or any other dynamically typed language since there’s no compilation time.
Progress means I don’t have to read blog posts in order to compile the kernel. Progress means I have a sane toolchain that lets me run, test, debug, manage dependencies, and even distribute my code and artefacts (documentation, compile output, …) easily. Progress means catching many more bugs at compile-time instead of runtime.
That’s you dawg. You probably have a different background, because I can follow zig code, but have no idea what a bunch of stuff means.
See samples
pub fn enqueue(this: *This, value: Child) !void {
,!void
? It’s important to returnvoid
? Watch outvoid
is being returned? Does that mean that you can write!Child
? And what would that even mean?const node = try this.gpa.create(Node);
what doestry
mean there? There’s nocatch
, noexcept
. Does that mean it just kills the stack and throws the exception until it reaches acatch/except
? If not, why put a try there? Is that an indication that it it can throw?node.* = .{ .data = value, .next = null };
excuse me what? Replace the contents of thenode
object with a new dict/map that has the keys.data
and.next
?if (this.end) |end| end.next = node //
what’s the lambda for? And what’s the//
for ? A forgotten comment or an operator? If it’s to escape newline, why isn’t it a backslash like in other languages?start: ?*Node
. Question pointer? A nullable pointer? But aren’t all pointers nullable? Or does zig make a distinction between zero pointers and nullable pointers?this.start orelse return null
is this a check for null or a check for 0 or both?However when I read rust the first time, I had quite a good idea of what was going on. Pattern matching and
move
were new, but traits were quite understandable coming from Java with interfaces. So yeah, mileage varies wildly and just because you can read Zig, doesn’t mean the next person can.Regardless, it’s not like either of us have any pull in the kernel (and probably never will). I fear for the day we let AI start writing kernel code…
Anti Commercial-AI license