This makes sense to me! Our components function as final classes anyway.

At one time, this would not have been desired behavior as there was a concept of using inheritance to make similar components that derived from a common interface. However, we have converged on the concept of using FPP style interfaces as the preferred method resulting in distinct components that share the same shape.

All this is to say, from a development perspective and an F Prime/FPP assumption perspective, this is likely preferred regardless of the value performance improvement. @timcanham @bocchino do you concur?

I'll also second this request, not just because of performance, but because it helps the C compiler detect missing port handlers sooner. If I compile just a single component, the build can succeed even if the component is missing a handler. (I won't hit an error until I construct an instance of the component in my topology.) If we include the final keyword by default, the missing handler will be caught very quickly when compiling the component.