On 7 June 2013 11:27, deadalnix <deadalnix@gmail.com> wrote:

On Friday, 7 June 2013 at 01:22:25 UTC, Walter Bright wrote:

On 6/6/2013 5:43 PM, Jakob Ovrum wrote:

On Friday, 7 June 2013 at 00:34:45 UTC, deadalnix wrote:

Yes, which happen anyway for shared objects !

This.

We can do whole-program-optimization to finalize
non-shared-library functions - and for shared-library functions
it doesn't make sense to finalize for performance - you're
trading one kind of indirection function call for another.

Can we all please address or recognize this?

Sure, but the trouble is determining which classes are going to be shared.

By requiring export for what can be shared. Can be enforced by
setting the visibility of the class's typeid.

But you realise that a shared library isn't EXCLUSIVELY shared, it is still used internally?

And the act of sharing it under your proposal means it can't be optimised ANYWHERE, even for internal usage.