Mikhail/scala edit #41
Conversation
sofiiako
left a comment
sofiiako
left a comment
There was a problem hiding this comment.
Thank you! Here's a couple of tiny suggestions
| This displays `1 2`. | ||
|
|
||
| For-loops translate similarly to for-expressions, but using the | ||
| *For* loops translate similarly to *for* expressions but use the |
There was a problem hiding this comment.
Probably would be better to enclose these in backtick quotes `` so that it is highlighted as code
There was a problem hiding this comment.
Right, I thought about it. Will fix it.
| - `T` is contravariant and appears only as a method parameter type | ||
| - `U` is covariant and appears only as a method result type | ||
|
|
||
| So the method is checks out OK. |
There was a problem hiding this comment.
I believe what they wanted to write was "So the method checks out OK", no?
There was a problem hiding this comment.
I thought a lot about this one, too. Just was not sure that "the method checks out OK" is quite idiomatic. But if it sounds ok to you, let's have it this way!
| A >: Reptile | ||
|
|
||
| The type parameter `A` that can range only over *supertypes* of `Reptile`. | ||
| The type parameter `A` can range over only the *supertypes* of `Reptile`. |
There was a problem hiding this comment.
Maybe "The type parameter A can range only over the supertypes of Reptile." ?
There was a problem hiding this comment.
Yes, I guess you're right.
Lazy Evaluation/Lazy Lists/task.md
Outdated
| methods (`filter`, `flatMap`...) are implemented in a way where the head is not being evaluated if is | ||
| not explicitly indicated. | ||
| methods (`filter`, `flatMap`, etc.) are implemented in a way where the head is not evaluated unless it is | ||
| explicitly required. |
There was a problem hiding this comment.
I would keep 'indicated' here at the end....
Also, could you please add `` to LazyList and `Stream` at the beginning of this paragraph?
There was a problem hiding this comment.
Good, will do that.
No description provided.