3 ms·
> there's nothing exactly preventing you from providing the wrong numbers and bad structs aside from the "higher layer in the stack" Right, mistakes are possib
by IshKebab 4y ago
> there's nothing exactly preventing you from providing the wrong numbers and bad structs aside from the "higher layer in the stack"
Right, mistakes are possible in both cases. But why pick the design that is more likely to lead to mistakes (on both sides of the interface) and is slower? There's just no good reason to do it like that.