Jordan Rose a69656f178 [Serialization] Don't crash if we can't get the type for an XREF (#12914) ...

If we can't resolve a cross-reference unambiguously, we're supposed to
produce an llvm::Error and let the calling code handle it. However, if
we couldn't even resolve the /type/ of the cross-reference, we would
just crash. Follow the supported error path in that case too -- in
many cases the error can just propagate upwards to something that can
handle it.

rdar://problem/34821187, plus an extra test case from
rdar://problem/35157494. (The latter will be fixed better later, but
meanwhile let's not regress on the crashing part.)

2017-11-15 09:32:48 -08:00

..

module.modulemap

[Serialization] Recover from ObjC protocols changing inheritance. (#11109)

2017-07-24 16:22:10 -07:00

Overrides.h

[Serialization] Don't crash if we can't get the type for an XREF (#12914)

2017-11-15 09:32:48 -08:00

ProtocolInheritance.h

[Serialization] Recover from ObjC protocols changing inheritance. (#11109)

2017-07-24 16:22:10 -07:00

Typedefs.h

[Serialization] Drop decls whose types can't be deserialized.

2017-04-27 18:30:34 -07:00

TypeRemovalObjC.h

[Serialization] Propagate errors through compound types.

2017-04-27 18:30:34 -07:00

Types.apinotes

Specifically mention version mismatches for non-subclassable classes.

2017-05-10 17:03:32 -07:00

Types.h

Specifically mention version mismatches for non-subclassable classes.

2017-05-10 17:03:32 -07:00