2015-07-07 16:24 GMT+09:00 Walter Bright via Digitalmars-d <digitalmars-d@puremagic.com>:

On 7/6/2015 3:52 PM, deadalnix wrote:

Unresolved types in the ABI ? Is that even possible ?

I don't remember the cases, but yes.

In old days, Type::merge() had generated mangled name even for TypeIdentifier.

It might be related to the topic.

---

Recently, a similar mangling definition issue around template instance had reported, but finally it's marked as invalid.

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

Current dmd uses __U for the front-end only instances, but it won't appear in the generated symbols.

It's just for the dmd-internal, so it's not documented in the spec.

I think we can take same approach.

As deadalnix pointed out, TypeIdentifier will never appear in any valid symbol names in object files. Therefore the definition would be dmd-internal specific, and can be removed from the spec.

Kenji Hara