November 24, 2018
https://issues.dlang.org/show_bug.cgi?id=9986

Stanislav Blinov <stanislav.blinov@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |stanislav.blinov@gmail.com

--- Comment #1 from Stanislav Blinov <stanislav.blinov@gmail.com> ---
Up to      2.062  : Success with output: ["std.stdio"]
2.063   to 2.064  : Success with output: ["std.algorithm", "std.stdio",
"std.traits"]
           2.065.0: Success with output: ["std.stdio"]
           2.066.0: Success with output: ["std.algorithm", "std.stdio",
"std.traits"]
2.067.1 to 2.074.1: Success with output: ["std.stdio"]
Since      2.075.1: Success with output: []

Regression?..

--
November 16, 2022
https://issues.dlang.org/show_bug.cgi?id=9986

Richard Cattermole <alphaglosined@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |alphaglosined@gmail.com
         Resolution|---                         |WONTFIX

--- Comment #2 from Richard Cattermole <alphaglosined@gmail.com> ---
importedModules is emitted based upon need.

It is used for module constructors being called in the right order.

The output right now is:

```
["std.array", "core.memory", "core.internal.array.utils"]
```

Unfortunately, you cannot use this for reflection purposes, as ModuleInfo is not always emitted (its bloat usually).

--