Problem with coupling shared object symbol visibility with protection

[Benjamin Thaut via Digitalmars-d]

On Wednesday, 28 January 2015 at 14:31:54 UTC, Dicebot wrote:

>
> Yes, I see the problem now. "static if" isn't even the worst 
> offender, any kind of string mixins that generate the call to 
> `bar` are impossible to detect without having actual `foo` 
> instance. Sorry for misinterpretation.
>
> With that in mind second option is starting to look more 
> attractive despite the grammar change - forcing good chunk 
> template API into structs does not sound very convenient :(

Well and then there is the third option Walter proposed:
- Make everything export even if it means that it gets callable 
by the user directly.