Skip to content

[ConstraintSystem] implement implicit pack materialization for abstract tuples instead of explicit '.element' #67292

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

sophiapoirier
Copy link
Contributor

No description provided.

@sophiapoirier sophiapoirier force-pushed the pack-stored-propety-shadows-global branch from 2b124cd to fa41015 Compare July 14, 2023 17:33
@sophiapoirier sophiapoirier changed the title name lookup bug when abstract tuple stored property shadows a global [ConstraintSystem] implement implicit pack materialization for abstract tuples instead of explicit '.element' Jul 14, 2023
@sophiapoirier
Copy link
Contributor Author

@swift-ci please test

emitDiagnostic(diag::pack_reference_outside_expansion,
packType);
auto patternType =
getPatternTypeOfSingleUnlabeledPackExpansionTuple(packType);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One note because I'll forget and it could totally be done separately - both InvalidPackReference and InvalidPackElement constructors should use resolveType(packType) and resolveType(packElementType) accordingly instead of just packType and packElementType, otherwise we'd end up with a diagnostic that could have type variables in it and crash.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants