Re: Import modules too verbose in some cases

2017-08-10 Thread Adam D. Ruppe via Digitalmars-d
On Wednesday, 9 August 2017 at 23:57:19 UTC, Johnson Jones wrote: Sometimes one doesn't want to import either the whole module nor specify a single function to import. There was a proposal called "dependency carrying declarations" about that, but a library trick was found to beat it:

Re: Import modules too verbose in some cases

2017-08-10 Thread Rene Zwanenburg via Digitalmars-d
On Wednesday, 9 August 2017 at 23:57:19 UTC, Johnson Jones wrote: Sometimes one doesn't want to import either the whole module nor specify a single function to import. It seems that basically D has all the info to import the function implicitly because it usually gives a nice error message

Import modules too verbose in some cases

2017-08-09 Thread Johnson Jones via Digitalmars-d
Sometimes one doesn't want to import either the whole module nor specify a single function to import. It seems that basically D has all the info to import the function implicitly because it usually gives a nice error message tells us which module to import for the function. e.g., A.B.C()