Fully-qualified symbol disambiguation is deprecated???

[Nick Sabalausky via Digitalmars-d-learn]

On 09/08/2016 06:22 PM, Nick Sabalausky wrote:
> On 09/08/2016 06:13 PM, Steven Schveighoffer wrote:
>> On 9/8/16 6:02 PM, Nick Sabalausky wrote:
>>> I'm getting deprecation messages ("Package...not accessible here,
>>> perhaps add static import") when simply trying to use fully-qualified
>>> symbol names to disambiguate a symbol. Is this really intended?
>>
>> Yes.
>>
>> It's difficult to attribute the message without context, though.
>
> Yea, unfortunately I don't have it narrowed down to a test case, atm.
>
>> And
>> there are still some straggling bugs which cause this message to be
>> erroneously printed.
>>
>
> I'm pretty sure I've hit one of those :( Can't be certain though until I
> examine my specific case further.
>

Turns out I didn't hit one of those bugs, but one of the problems I was 
hitting was the old problem where package.d completely fucks any and all 
attempts at using a FQN. Worked around with local selective renamed imports.

FQN used to be a real killer feature of D: To deal with name collisions, 
you could *ALWAYS* replace a visible symbol with it's FQN and it would 
*just work*. But now with package.d, UFCS, and 2.071's selective import 
behavior, that benefit's pretty much been shot to hell.