Skip to content
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

Type applications with no arguments should not be accepted #4

Closed
io7m opened this issue Dec 22, 2020 · 0 comments
Closed

Type applications with no arguments should not be accepted #4

io7m opened this issue Dec 22, 2020 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@io7m
Copy link
Member

io7m commented Dec 22, 2020

An expression such as this:

[IntegerUnsigned32]

... shouldn't be accepted. The actual expression should be rejected as a type error, as it's a function application applied to a type constructor that takes no arguments.

@io7m io7m added the bug Something isn't working label Dec 22, 2020
@io7m io7m self-assigned this Dec 22, 2020
@io7m io7m closed this as completed in 71aea36 Dec 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant