-
Notifications
You must be signed in to change notification settings - Fork 73
Split Predicate into Goal and Clause #531
Copy link
Copy link
Closed
Labels
T-compilerAdd this label so rfcbot knows to poll the compiler teamAdd this label so rfcbot knows to poll the compiler teammajor-changeA proposal to make a major change to rustcA proposal to make a major change to rustcmajor-change-acceptedA major change proposal that was acceptedA major change proposal that was accepted
Metadata
Metadata
Assignees
Labels
T-compilerAdd this label so rfcbot knows to poll the compiler teamAdd this label so rfcbot knows to poll the compiler teammajor-changeA proposal to make a major change to rustcA proposal to make a major change to rustcmajor-change-acceptedA major change proposal that was acceptedA major change proposal that was accepted
Type
Fields
Give feedbackNo fields configured for issues without a type.
Proposal
Chalk and a-mir-formality have the concept of
GoalandClausethat wrap certain subsets of what currently isPredicateto differentiate between things that need to be proven (e.g. when invokingx + y, a goaltypeof(x): Add<typeof(y)>is introduced) and things that we know must hold (where clauses and implied bounds, essentially theParamEnv).Doing this will remove differences between rustc trait solving and chalk, and paves the way for properly checking higher kinded lifetime bounds (it would be possible without this, but it's annoying and not making the code more readable).
Mentors or Reviewers
Process
The main points of the Major Change Process are as follows:
@rustbot second.-C flag, then full team check-off is required.@rfcbot fcp mergeon either the MCP or the PR.You can read more about Major Change Proposals on forge.
Comments
This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.