Bug 20172 – using functions with full path and without preliminary import

sometimes imported functions used in simple context suggestion: add possibility to use imported function in-situ with full path struct S { void freeItem( void* pelem ) { // now: u should import before call //import core.stdc.stdlib : free; // no needed // suggestion: just call core.stdc.stdlib.free( pelem ); } } full path modules.func( .. ) tells exactly function that needed with less LOC, key press and without blurring eyes by 2 separate items: import and invoke

Is foo.bar.baz referring to the free function baz in the module foo.bar, or the member baz in the type bar in the module foo? In addition to this ambiguity, this effectively turns every typo into an expensive file system lookup.

(In reply to Simen Kjaeraas from comment #1) > Is foo.bar.baz referring to the free function baz in the module foo.bar, or > the member baz in the type bar in the module foo? In addition to this > ambiguity, this effectively turns every typo into an expensive file system > lookup. in any case u(D gods) can extend syntax core.stdc.stdlib:free( pelem ) foo.bar:baz colon":" that split module path from type.method path meaning left be same as now but shorter in 1LOC