Is it a bug that a parent class that access its own private members from derived classes gets deprecation warning?

[user1234]

On Saturday, 7 April 2018 at 20:46:39 UTC, bauss wrote:
> On Saturday, 7 April 2018 at 20:34:57 UTC, user1234 wrote:
>> On Saturday, 7 April 2018 at 20:14:49 UTC, bauss wrote:
>>> jesus that became a long title.
>>>
>>> Anyway as the title says, is it a bug that a parent class 
>>> that access its own private members from derived classes gets 
>>> deprecation warning?
>>
>> If the import is selective no. (`import foo : Foo;`)
>> If the import is for the whole module i'd say yes. (`import 
>> foo;`)
>
> What do you mean?
>
> The problem is that "Foo" cannot access "_baz" without 
> deperecation warning, but "_baz" is a part of "Foo".

_baz is private and not protected. The deprecation was introduced 
because bug 314 broke the private protection.