You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For module aliasing, we changed the product lookup to include package identity, but product references can use a local identity as specified by the `name` attribute of the package dependency declaration. So for packages where the local `name` attribute didn't match the identity, we would not longer find the corresponding products at all. This switches us back to use the local identity that is also called `explicitNameForTargetDependencyResolutionOnly` in package reference.
rdar://106578471
throwInternalError("could not determine name for dependency on package '\($0.packageBuilder.package.identity)' from package '\(packageBuilder.package.identity)'")
@@ -962,6 +971,9 @@ private final class ResolvedPackageBuilder: ResolvedBuilder<ResolvedPackage> {
962
971
/// The dependencies of this package.
963
972
vardependencies:[ResolvedPackageBuilder]=[]
964
973
974
+
/// Map from package identity to the local name for target dependency resolution that has been given to that package through the dependency declaration.
0 commit comments