mirror of
https://github.com/apple/swift.git
synced 2025-12-14 20:36:38 +01:00
Hack around this instead by using the two-function form of subst(), and checking if the generic parameter is valid in the signature. This comes up because we're using the generic signature of the nominal type to get a SubstitutionMap, and then applying this map to the types in the generic requirements of a member. If the member introduces its own generic parameters, some of those requirements might not be valid types in the outer generic signature. This can probably use SubstitutionMap::combineSubstitutionMaps() instead, but it would require more refactoring than I'm willing to undertake for now.
54 KiB
54 KiB