Re:Data-oriented design or why you might shoot yourself in t...
by duped on Monday June 28, 2021 @01:19PM
(#27664630)
Enormously slower function calls and zero inlining without advanced dynamic compilation, which has a number of pitfalls.
[ Parent
| on HN ]
Re:Data-oriented design or why you might shoot yourself in t...
by kaba0 on Monday June 28, 2021 @05:37PM
(#27668522)
As opposed to passing function pointers everywhere, callback hell and friends? Or which language does it well in your opinion? The fact is, dynamic dispatch is needed, because not everything can be known at compile time. And as in a recent thread a HNer rightly noted (could not find it where I read it), the actually expensive thing in programming is flexibility.
Re:Data-oriented design or why you might shoot yourself in t...
by throwaway894345 on Monday June 28, 2021 @02:07PM
(#27665345)
Devirtualization optimizations can turn semantically "dynamic" dispatches into static dispatches, but sometimes you really just need a dynamic dispatch. Note that a dynamic dispatch doesn't have to be anything more than a branch. Further, sometimes devirtualizing everything leads to enormous binaries and compile times. Runtime performance isn't everything, and it's typically better to opt-into devirtualization rather than to opt-out of it.
Re:Data-oriented design or why you might shoot yourself in t...
by bccdee on Monday June 28, 2021 @03:59PM
(#27667079)
You must have absurd standards if you find dynamic dispatch to be unacceptably slow. Also, yeah, not every function call needs to be inlined. One level of indirection on top of jumping into a new function isn't really much overhead at all, unless you're doing it for literally every function call.