On 12/08/2017 12:10 PM, mrphobby wrote:
> I still think using the word "import" is confusing. Would rather have it
> called "load" or something. But at least I understand it now :)
We don't want any more keywords. :) (D's keywords are context-independent.)
An unfortunate example was the "body",
On Thursday, 7 December 2017 at 09:47:31 UTC, Jacob Carlborg
wrote:
On 2017-12-06 20:05, mrphobby wrote:
There are two kinds of language constructs that uses the
"import" keyword. One is the "Import Declaration" [1] which is
the most common one and is used to import other symbols. The
other la
On 2017-12-06 20:05, mrphobby wrote:
Can anyone explain what "stringImportPaths" is? I have seen this being
used in dub.json files and I think I kind of know what it does, but I
haven't been able to find a clear explanation in any documentation of
what it does. It does not look like anything I'
On Wednesday, 6 December 2017 at 20:17:55 UTC, Ali Çehreli wrote:
On 12/06/2017 11:05 AM, mrphobby wrote:
> importing is a construct used for importing symbols, right?
That's the import statement. -J compiler switch is about the
import expression:
https://dlang.org/spec/expression.html#imp
On Wednesday, 6 December 2017 at 19:05:24 UTC, mrphobby wrote:
Can anyone explain what "stringImportPaths" is? I have seen
this being used in dub.json files and I think I kind of know
what it does, but I haven't been able to find a clear
explanation in any documentation of what it does. It does
On 12/06/2017 11:05 AM, mrphobby wrote:
> importing is a construct used for importing symbols, right?
That's the import statement. -J compiler switch is about the import
expression:
https://dlang.org/spec/expression.html#import_expressions
Ali
Can anyone explain what "stringImportPaths" is? I have seen this
being used in dub.json files and I think I kind of know what it
does, but I haven't been able to find a clear explanation in any
documentation of what it does. It does not look like anything I'm
familiar with from other languages.
