Access specifiers and visibility

[John Colvin via Digitalmars-d-learn]

On Wednesday, 10 May 2017 at 01:42:47 UTC, Andrew Edwards wrote:
> Attempting to update a git repo to current D, I encounter the 
> following deprecation messages:
>
> src/glwtf/signals.d-mixin-256(256,2): Deprecation: 
> glwtf.input.BaseGLFWEventHandler._on_key_down is not visible 
> from module glwtf.signals
> src/glwtf/signals.d-mixin-256(256,2): Deprecation: 
> glwtf.input.BaseGLFWEventHandler._on_key_up is not visible from 
> module glwtf.signals
> src/glwtf/signals.d-mixin-256(256,2): Deprecation: 
> glwtf.input.BaseGLFWEventHandler._on_mouse_button_down is not 
> visible from module glwtf.signals
> src/glwtf/signals.d-mixin-256(256,2): Deprecation: 
> glwtf.input.BaseGLFWEventHandler._on_mouse_button_up is not 
> visible from module glwtf.signals

Those error messages are often misleading. The name of the symbol 
alone is (often, always?) right but the module/package it says 
it's from is often nonsense. I often get deprecation messages 
saying things like "myPackage.myModule.to is not visible from 
module myPackage.myOtherModule", when the real problem is I 
forgot to import std.conv in myPackage.myOtherModule.