News for hackers. Stuff that matters.
Re:Zig: Build System Reworked by nullpoint420 on Saturday May 30, 2026 @11:34AM (#48337333)
Wow that’s gnarly it’s using dynamic dispatch. I mean I get it, but I thought zig was some sort of performance demon.
Re:Zig: Build System Reworked by dnautics on Saturday May 30, 2026 @12:10PM (#48337769)
if youre doing io, one pointer indirection seems unlikely tp be rate limiting. same for allocation (the other dynamic dispatch in zig)
Re:Zig: Build System Reworked by lukaslalinsky on Saturday May 30, 2026 @04:21PM (#48340240)
It's not just I/O, it's also mutexes, condition variables, time, etc. It's not horrible, but it does add up, so calling it super efficient is a stretch.
Re:Zig: Build System Reworked by kimixa on Sunday May 31, 2026 @12:43AM (#48343088)
A modern allocator with per-thread cache can satisfy some allocations in 20-30 cycles - dynamic dispatch can easily double that, even if the target is still in cache.

It's one of these things where it's extremely use case dependant - like many performance issues, you probably don't care about it - but when you do it matters.

Re:Zig: Build System Reworked by delamon on Sunday May 31, 2026 @04:01AM (#48343881)
Inderect call cost is a few cycles, if predicted. Now, you can argue, that it may be mispredicted and misprediction would cost about 20-30 cycles. But if it is mispredicted, then you are not calling into allocator often enough. And if you don't hammer it hard, then why do you care about preformance?
Re:Zig: Build System Reworked by smj-edison on Saturday May 30, 2026 @02:11PM (#48339098)
I believe their plan is using "restricted function pointers", where you can specify that a pointer will only ever be to a function defined in the codebase. I'm pretty sure they also have plans for devirtualization, but I haven't followed super closely.
Re:Zig: Build System Reworked by dnautics on Saturday May 30, 2026 @07:16PM (#48341519)
"you can specify that a pointer"

i dont think you need to specify that. the compiler can figure it out and do an optimization pass at the end.

Re:Zig: Build System Reworked by smj-edison on Saturday May 30, 2026 @09:32PM (#48342273)
Oh, is it not a specific keyword? I thought they were thinking of it being a keyword so you could be sure that it was restricted, in case a variable or function was exported that took in a foreign pointer.
Re:Zig: Build System Reworked by lukaslalinsky on Saturday May 30, 2026 @11:45PM (#48342855)
There are going to be builtins to control this. The compiler will not do it on its own.