Skip to content

TypeResolution: Map any constraint into context before checking validity #79296

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

Closed
wants to merge 2 commits into from

Conversation

AnthonyLatsis
Copy link
Collaborator

  • In the structural stage, let the constaint type be if it is a type parameter. We do not have enough information to prove it invalid.
  • In the interface stage, first map the constraint type into context, and only then proceed to validation.

…idity

* In the structural stage, let the constaint type be if it is a type
  parameter. We do not have enough information to prove it invalid.
* In the interface stage, first map the constraint type into context,
  and only then proceed to validation.
@AnthonyLatsis
Copy link
Collaborator Author

@swift-ci please smoke test macOS

@AnthonyLatsis
Copy link
Collaborator Author

Attempting to supersede with #79322.

@AnthonyLatsis AnthonyLatsis deleted the anopheles-gambiae branch February 14, 2025 03:36
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