Jordan Rose c1c4f5243b [Mangling] Include private discriminators in constructor manglings. (#9880) ...

Previously, two constructors with the same full name and argument
types would get identical manglings even if they were declared
'private' or 'fileprivate' in different files. This would lead to
symbol collisions in whole-module builds. Add a new mangling node for
private discriminators on base-name-less decls to make this unique.

This still doesn't fix the existing issue with private members, named
or not, conflicting when they're in the /same/ file, but since Swift 4
makes those members visible to one another (SE-0169) that's only an
issue in Swift 3 mode anyway, and as such probably won't get fixed at
all.

rdar://problem/27758199

2017-06-01 16:42:17 -07:00

..

CMakeLists.txt

Switch back to the old mangling for ObjC runtime names.

2017-05-03 10:52:54 -07:00

Context.cpp

demangler: classify reabstruction thunks as thunks

2017-05-11 16:02:21 -07:00

Demangler.cpp

[Mangling] Include private discriminators in constructor manglings. (#9880)

2017-06-01 16:42:17 -07:00

ManglingUtils.cpp

rename namespace NewMangling -> Mangle

2017-03-20 10:09:30 -07:00

NodeDumper.cpp

demangling: Drop the support of "unmangled suffix"

2017-05-24 17:00:20 -07:00

NodePrinter.cpp

[Mangling] Include private discriminators in constructor manglings. (#9880)

2017-06-01 16:42:17 -07:00

OldDemangler.cpp

Demangler: make the demangler more tolerant with malformed symbols.

2017-05-16 12:28:32 -07:00

OldRemangler.cpp

Mangling: use ‘Tm’ mangling for merged functions

2017-05-24 17:00:16 -07:00

Punycode.cpp

rename namespace NewMangling -> Mangle

2017-03-20 10:09:30 -07:00

Remangler.cpp

[Mangling] Include private discriminators in constructor manglings. (#9880)

2017-06-01 16:42:17 -07:00