-
-
Notifications
You must be signed in to change notification settings - Fork 14.9k
Change opaque types to not be structural match. #72156
Copy link
Copy link
Closed
Labels
C-bugCategory: This is a bug.Category: This is a bug.F-type_alias_impl_trait`#[feature(type_alias_impl_trait)]``#[feature(type_alias_impl_trait)]`T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Metadata
Metadata
Assignees
Labels
C-bugCategory: This is a bug.Category: This is a bug.F-type_alias_impl_trait`#[feature(type_alias_impl_trait)]``#[feature(type_alias_impl_trait)]`T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
Status
Done
The following currently passes the structural match check and causes an ICE later on:
(now that #72153 has landed, this emits an error)
I believe we have to either leak the structural match property of opaque types,
(similar to
SendandSyncafaict) or forbid this entirely.I am in favor of the second option for now. It should not be a breaking change to go from the
second to the first later on.
This issue concerns the implementation in #72153
@eddyb @pnkfelix @RalfJung