5 ms·
I'm not sure why you keep steering the conversation to Rust. It doesn't matter how doomed Rust's Read trait is. Zig is a totally different language. Zig is not
by TakeBlaster16 4y ago
I'm not sure why you keep steering the conversation to Rust. It doesn't matter how doomed Rust's Read trait is. Zig is a totally different language. Zig is not bound by the same design tradeoffs. That is why it's possible for Zig to have generic functions in its Reader interface, such as today's `readInt`, or tomorrow's `readAllArrayList`.
- Arnavion 4y agoMate, I'm not "steering" the conversation to Rust. The paragraph you responded to was about Rust in the first place. I clearly said there are two downsides of having the Allocator be part of the type. One, the busywork from having to propagate the type parameter, applies to Zig and Rust. The other, the fact that generic methods can't go in vtables, only applies to Rust.