[Issue 16994] Apparently faulty symbol resolution in some cases

2017-01-08 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16994 Martin Nowak changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 16994] Apparently faulty symbol resolution in some cases

2017-01-08 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16994 --- Comment #3 from Martin Nowak --- Seems to be a duplicate of issue 14894, only in this case the 2 compilations produce different functions with the same mangling instead of causing a linker error. It just happens that in both compilations a lambda

[Issue 16994] Apparently faulty symbol resolution in some cases

2017-01-08 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16994 --- Comment #2 from Martin Nowak --- Only happens with rdmd's double compilation mode, https://github.com/dlang/tools/pull/194, which firsts builds object for the root module, then builds another (single) object for all dependencies. That PR caused a

[Issue 16994] Apparently faulty symbol resolution in some cases

2017-01-08 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16994 Martin Nowak changed: What|Removed |Added CC||c...@dawg.eu Hardware|x86