if the dispatches do use vtable they won't be inline and won't be faster. The real deal is inlining when necessary, which inheritance doesn't really prevent.
No, Java does Class hierarchy analysis and has multiple way not to use v-table calls.
Single site (no class found overriding a method) are static and can be inlined directly. Dual call sites use a class check (which is a simple equality), can be inlined, no v-table. 3-5 call sites use inline caches (e.g. the compiler records what class have been used) that are similar and some can be inlined, usually plus a guard check.
Only high polymorphic calls use v-table and in practice is a very rare occasion, even with Java totally embracing inheritance (or polymorphic interfaces)
Note: CHA is dynamic and happens at runtime, depending which classes have been loaded. Loading new classes causes CHA to be performed again and if there are affected sites, the latter are to be deoptimized (and re-JIT again)
Java strings enjoy heavy optimizations, including SSE4.2 and AVX intrinsics. Implementing your own byte[] wrappers (which Strings are) might be useful however it won't replace the built-in Strings.
In short: a general purpose String substitute in Java would be an extremely poor idea.
no, mmap is a system call; the memory allocators tend not to use syscalls (often at all) as objection instantiation is very common; also it has to be concurrent and what not.
Both allow to have software developed for by any 3rd parties - that should include any and the original device seller should not be able to control the distribution.
If you really ask: xbox is pretty much the same as an x86-64 PC, running Windows (and having AMD GPU). It just bit more sealed.
Indeed, I don't see any need to have a tree as a language primitive along with a traversal function (iterator). Tree traversal is not really different than iterating over a vector/list. E.g. even java has stuff like: TreeSet.forEach(consumerRef) or for(Type val : tree) doStuffWith(val)
Trees are an insignificant middle ground between lists (which, by the way, are degenerate trees) and general iterators (on general object graphs, or not even materialized).
English is not my native language. I am referring to fatigue caused by thermal cycling. Annealing for one year is done to test the chemical stability of the alloy and ensure that there is no migration or segregation of alloy elements.
There may be unstable hydrodynamic phenomena in a pipe or heat exchanger, which generates a large number of thermal cycles. Such as the instability of a vortex in a mixing or heat exchange zone.
This is a different ageing mechanism. It is very complicated and time-consuming to test in the laboratory.
So, you still need to run some perf. testing on your own to decide.
reply