On Monday, 17 November 2014 at 03:22:49 UTC, Meta wrote:
It seems like a feature to me. Otherwise, you would have A.foo, which is in module a, calling a private function from module b. I think it is sane that the function should be public if you want to do things such as this. Furthermore, it will stop you from accidentally passing private symbols to alias template arguments when you don't mean to.
Obviously this is gonna call the private function, that is the whole point. What would be the benefit of preventing me to do that ? Stating that it would prevent me to do it do not explain why I wouldn't want that.
