[Issue 14050] `dmd -v` lists imports from failed __traits(compiles) blocks

2015-06-09 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14050

Andrei Alexandrescu and...@erdani.com changed:

   What|Removed |Added

Version|unspecified |D2

--


[Issue 14050] `dmd -v` lists imports from failed __traits(compiles) blocks

2015-01-26 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14050

--- Comment #2 from github-bugzi...@puremagic.com ---
Commits pushed to master at https://github.com/D-Programming-Language/dmd

https://github.com/D-Programming-Language/dmd/commit/451a54b331e9ce49a5cd32fc5ebe7eddd7a8ec18
fix Issue 14050 - `dmd -v` lists imports from failed __traits(compiles) blocks

Don't print verbose message if module load fails.

https://github.com/D-Programming-Language/dmd/commit/8a04bc489dc9272ccb64f4739d0cf93fd5b08fd7
Merge pull request #4346 from 9rnsr/fix14050

fix Issue 14050 - `dmd -v` lists imports from failed __traits(compiles) blocks

--


[Issue 14050] `dmd -v` lists imports from failed __traits(compiles) blocks

2015-01-26 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14050

--- Comment #3 from Dicebot pub...@dicebot.lv ---
Thanks, that was lightning quick!

 If it's a problem, please open a new issue.

Done : https://issues.dlang.org/show_bug.cgi?id=14052

--


[Issue 14050] `dmd -v` lists imports from failed __traits(compiles) blocks

2015-01-26 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=14050

Kenji Hara k.hara...@gmail.com changed:

   What|Removed |Added

   Keywords||pull

--- Comment #1 from Kenji Hara k.hara...@gmail.com ---
https://github.com/D-Programming-Language/dmd/pull/4346

---

-deps has similar issue, but i'm not sure it should be fixed.

Compiles OP code with:

dmd -deps -o- test

Prints:

DMD v2.067 DEBUG
not importing missing
depsImport test (test.d) : private : object
(C:\\dmd2\\src\\druntime\\import\\object.di)
depsImport test (test.d) : private : missing (???) 

If it's a problem, please open a new issue.

--