Hmm in the 2025 talk ( https://youtu.be/f30PceqQWko?si=qZESxMaSyt7fYMfz ), Andrew emphasizes that this approach is more efficient than before- even showing compiled assembly iirc. I guess that was a one-off?
replyMy guess is that one of these (Andrew) is measuring syscalls and the other is measuring vtable indirections.
replyA vtable indirection is essentially free when you're going to perform a syscall. What matters is that the buffer is above the vtable (which is already the case for the current implementation) so that you don't pay for the indirection when hitting the buffer.
replyWow that’s gnarly it’s using dynamic dispatch. I mean I get it, but I thought zig was some sort of performance demon.
replyif youre doing io, one pointer indirection seems unlikely tp be rate limiting. same for allocation (the other dynamic dispatch in zig)
replyThe parent seems to be talking about efficient code style, not necessarily performance implementation, as they go on to discuss how it looks.
replyThat is, I think the point was DevX not io performance.