DIP10005: Dependency-Carrying Declarations is now available for community feedback

[Meta via Digitalmars-d]

On Tuesday, 20 December 2016 at 14:31:38 UTC, Dmitry Olshansky 
wrote:
> On 12/13/16 11:33 PM, Andrei Alexandrescu wrote:
>> Destroy.
>>
>> https://github.com/dlang/DIPs/pull/51/files
>>
>>
>> Andrei
>
> Just a thought but with all of proliferation of imports down to 
> each declaration comes the pain that e.g. renaming a module 
> cascades to countless instances of import statements. This is 
> true of local imports as well but the problem gets bigger.
>
> ----
> Dmitry Olshansky

Could you not have the old module just be empty and publicly 
import the new one, and also deprecate it so people have time to 
change their code? Also having special syntax makes finding every 
occurrence of an inline import a fairly simple search.