Problem with coupling shared object symbol visibility with protection

[Dicebot via Digitalmars-d]

On Sunday, 1 February 2015 at 09:24:46 UTC, Benjamin Thaut wrote:
>> So you'd want bar to be duplicated on both sides ? This is 
>> gonna cause
>> problems with di files.
>
> No. He wants the compiler to automatically detect that the 
> template foo might call bar. As a result the compiler should 
> export bar when compiling the shared library so that any user 
> of foo does not run into a "unresolved symbol reference" linker 
> error. Bar would still only exist once: within the shared 
> library.

Correct. Sadly it won't work that way as I was already pointed at.
Otherwise it is perfect solution :P