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.

Sign up for GitHub

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

Fix a couple of typos in scala-for-java-programmers.md #3177

Merged
merged 1 commit into from
Mar 23, 2025
Merged

Fix a couple of typos in scala-for-java-programmers.md #3177

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions _overviews/tutorials/scala-for-java-programmers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -506,7 +506,7 @@ to omit types, and when to specify them explicitly.
### Methods without arguments

A small problem of the methods `re` and `im` is that, in
order to call them, one has to put an empty pair of parenthesis after
order to call them, one has to put an empty pair of parentheses after
their name, as the following example shows:

{% tabs method-call-with-args-demo class=tabs-scala-version %}
Expand Down Expand Up @@ -811,7 +811,7 @@ code which typically makes use of these named parts.

A programmer familiar with the object-oriented paradigm
might wonder why define a single function for `eval` outside
the scope of `Tree`, and not make `eval` and abstract method in
the scope of `Tree`, and not make `eval` an abstract method in
`Tree`, providing overrides in each subclass of `Tree`.

We could have done it actually, it is a choice to make, which has
Expand Down