On 9/28/21 1:59 AM, james.p.leblanc wrote:
On Tuesday, 28 September 2021 at 05:26:29 UTC, Ali Çehreli wrote:
On 9/27/21 10:38 AM, james.p.leblanc wrote:
In addition to what Mike Parker said, templates do complicate matters
here: Templates are instantiated (i.e. compiled for a specific set o
On Tuesday, 28 September 2021 at 05:26:29 UTC, Ali Çehreli wrote:
On 9/27/21 10:38 AM, james.p.leblanc wrote:
In addition to what Mike Parker said, templates do complicate
matters here: Templates are instantiated (i.e. compiled for a
specific set of template arguments) by modules that actua
On Tuesday, 28 September 2021 at 02:05:43 UTC, Mike Parker wrote:
On Monday, 27 September 2021 at 17:38:29 UTC, james.p.leblanc
mpilations".
Does that help?
**Yes!...**
===
... this helped immensely!
This explanation gave me a much better understanding of how the
whole process works.
On 9/27/21 10:38 AM, james.p.leblanc wrote:
> I have trouble understanding "module imports" vs. "module compilations".
In addition to what Mike Parker said, templates do complicate matters
here: Templates are instantiated (i.e. compiled for a specific set of
template arguments) by modules that
On Monday, 27 September 2021 at 17:38:29 UTC, james.p.leblanc
wrote:
Dear D-ers,
I have trouble understanding "module imports" vs. "module
compilations".
A module is implemented in a source file. Though we often use the
term "module" to refer to both, it may help to think in terms of
import
Dear D-ers,
I have trouble understanding "module imports" vs. "module
compilations".
For example, in the dlang.org/tour, we have:
**"The import statement makes all public functions and types from
the given module available."**
And from the dlang.org/spec we have:
**"Modules are always com
