Skip to content

update parameterlists #1652

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

Merged
merged 4 commits into from
Apr 5, 2020
Merged

Conversation

martijnhoekstra
Copy link
Contributor

Update tour section for multiple parameterlists.

I wasn't able to understand the text in a way that actually reflected how scala worked, so I re-wrote it entirely. Should close #1647 that was also confused about what the intent was.

@zuliandri2 is this more helpful than the original?

@martijnhoekstra
Copy link
Contributor Author

based on the feedback, and re-reading what I wrote, I expanded on what is inferred and why a bit more.

```

this would not be possible with only a single parameter list, as the Scala compiler would not be able to infer the parameter types of the function.
This definition doesn't need any type hints and can infer all of its parameters.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/parameters/type parameters/

@martijnhoekstra martijnhoekstra force-pushed the curryingUpdate branch 4 times, most recently from 140d48a to 05a797e Compare March 30, 2020 19:29
@SethTisue SethTisue merged commit 9eeaa6d into scala:master Apr 5, 2020
@SethTisue
Copy link
Member

thanks Martijn!

@martijnhoekstra martijnhoekstra deleted the curryingUpdate branch March 16, 2021 11:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Tour: it's not immediately clear the hypothetical foldLeft with a single parameterlist doesn't compile
2 participants