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
First issue: currently, non-defining uses of TAIT in the defining scope are not allowed; see this comment.
Second issue: defining usage via a struct field.
Related cases:
compound type aliases are already supported: type B = (A, ()); where A is TAIT (also applies to array types)
enum usages usually (when N>1) do not involve all variants and often do not involve all type-components, so extension to enum would only be possible in very limited circumstances: already supported for Option but not other enums
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Sub-issue of #63063
It should be possible for the defining implementation of Type-Alias-Impl-Trait (aka TAIT) to be a struct usage:
First issue: currently, non-defining uses of TAIT in the defining scope are not allowed; see this comment.
Second issue: defining usage via a struct field.
Related cases:
type B = (A, ());
whereA
is TAIT (also applies to array types)enum
usages usually (when N>1) do not involve all variants and often do not involve all type-components, so extension toenum
would only be possible in very limited circumstances: already supported for Option but not other enumsThe text was updated successfully, but these errors were encountered: