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

Repeated 'fnty' in curried function types #188

Open
gribozavr opened this issue Nov 10, 2020 · 3 comments
Open

Repeated 'fnty' in curried function types #188

gribozavr opened this issue Nov 10, 2020 · 3 comments
Labels
leads question A question for the leads team long term Issues expected to take over 90 days to resolve.

Comments

@gribozavr
Copy link
Contributor

According to the grammar in the basic syntax proposal (#162) it seems like curried function types require repeating the fnty keyword:

expression:  "fnty" tuple return_type
return_type:  "->" expression

For example:

fnty (Int) -> Int // OK
fnty (Int) -> fnty (Int) -> Int // repeated fnty
fnty (Int) -> (Int) -> Int // desired

I understand why it happens, and I see that it is uniform with regards to the expression production, but the result -- repeated fnty keywords -- does not seem aesthetically pleasing to me.

@gribozavr gribozavr mentioned this issue Nov 10, 2020
@jonmeow
Copy link
Contributor

jonmeow commented Nov 10, 2020

Note, "Should there be a function type? #191" may supersede this issue.

@jsiek
Copy link
Contributor

jsiek commented Feb 28, 2021

This issue with repeated fnty a good observation. Certainly a disadvantage of the current syntax.

@github-actions
Copy link

We triage inactive PRs and issues in order to make it easier to find active work. If this issue should remain active or becomes active again, please comment or remove the inactive label. The long term label can also be added for issues which are expected to take time.
This issue is labeled inactive because the last activity was over 90 days ago.

@github-actions github-actions bot added the inactive Issues and PRs which have been inactive for at least 90 days. label Jul 30, 2021
@jonmeow jonmeow added long term Issues expected to take over 90 days to resolve. leads question A question for the leads team and removed inactive Issues and PRs which have been inactive for at least 90 days. labels Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
leads question A question for the leads team long term Issues expected to take over 90 days to resolve.
Projects
None yet
Development

No branches or pull requests

3 participants