A modern programming language that makes developers happier.

kotlinlang

When it comes to iteration and ranges one can write something like:
```
    (5 downTo 3  step 3).forEach { println(it) }
```
or
```
    (5 downTo 3).filter { it % 2 == 0}
        .forEach { println(it) }
```
However, if filter would be infix, one could also write
```
    (5 downTo 3  filter { it % 2 == 0})
        .forEach { println(it) }
```
which would be totally in sync with the infix syntax of `step`, and possibly would mean a more consistent API. Any thoughts?

Well, that was a nice discussion with good arguments, <@U2E974ELT>.:)

I don’t have any arguments for this discussion, sorry. 

I see `filter` as a more general construct. It works on collections, sequences, streams etc.
`step` on the other hand is specific to progressions, that's probably why it has an infix version – to enable the use like in your first example.

<@U61EJ4P4J> That is a good point and argument. I think, discussing things is always a better approach than just using power. At least this is the way we work in Norway. I know, that countries and cultures differ.

Sorry, I did not mean to use power. I wanted to express my opinion (dislike of the idea) while lacking arguments to explain what exactly I did not like.  

There was a time when there was no `infix` modifier in Kotlin and every function with a receiver and one parameter was eligible to be called as infix.
Then we decided we want make these things explicit and require that modifier to designate a function being callable in the infix form. That raised a question which of the standard functions should remain callable as infix.
For the functions like `filter`, `map`, and so on, we concluded it would be more consistent to invoke them always with a dot, rather than to allow both call forms and burden users with a decision which one to use in their particular case.

<@U0AAQKT9Q> why was the decision to take off default infix behavior and add the keyward taken?

See the "Operators and infix functions" section here: <https://blog.jetbrains.com/kotlin/2015/09/call-for-feedback-upcoming-changes-in-kotlin/>