Skip to content

co19_2/LanguageFeatures/Instantiate-to-bound/nonfunction_typedef/dynamic/nonfunction_l2_t08 expectation #502

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
eernstg opened this issue Nov 21, 2019 · 0 comments
Assignees
Labels
type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@eernstg
Copy link
Member

eernstg commented Nov 21, 2019

Said test expects a specific raw type, but the type alias should be a compile-time error because its declared bounds do not ensure that the type arguments are appropriate for the body.

That is, we can't use X1 <: X2, X2 <: B<X1, X2> to prove that X1 <: B<X1, X2>, as required in order to make the body of the type regular-bounded.

Cf. this text, which says that the body of a type alias must be regular-bounded when the type arguments to the type alias satisfy their bounds.

@eernstg eernstg added the type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) label Nov 21, 2019
@iarkh iarkh self-assigned this Nov 22, 2019
iarkh added a commit that referenced this issue Nov 25, 2019
…ef bounds do not ensure that the type arguments are appropriate for the body.
iarkh added a commit that referenced this issue Nov 25, 2019
…ef bounds do not ensure that the type arguments are appropriate for the body.
@iarkh iarkh closed this as completed Nov 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Development

No branches or pull requests

2 participants