visibility vs. accessibility of protected symbols

[Timon Gehr]

On 02/14/2012 01:55 AM, Timon Gehr wrote:
>
> There are no performance implications because the compiler has the whole
> module ready to analyse. Therefore it can de-virtualise any calls to
> private members that are never overridden. A trivial addition to the
> class layout could furthermore allow the compiler to remove the vtable
> entry for such a member function entirely (essentially, virtual private
> members would get negative vtable offsets). I actually think that should
> be implemented in order to get a potential TDPL error off the table.
>

Nevermind, separate compilation could get tricky.