The Dot Operator

Andrey Breslav

Warning: this is an April Fools’ post

Point-free style is a big trend in modern functional programming: it allows to manipulate functions without mentioning their arguments which makes the code concise and compositional. Here is an example from Wikipedia:

mf = (. map) . (.) . filter

This function, written in Haskell, composes a map() function with a filter() function. As you can see, point-free style largely relies on dots.

Kotlin is not a functional language per se, but we are happy to borrow useful features from other languages. So, today I’ll write about dots.

The Dot

We introduce the dot operator in Kotlin. As usual, it works by convention. If there’s a function like this

fun {
    println("a dot!")

it will be called whenever there’s a dot (“.”) after an expression of type Foo:

fun test(f: Foo) {

This function prints “a dot!” twice: once for each dot after a Foo. The bar() function doesn’t return a Foo, so the dot after it doesn’t count.

Dot Chaining

What if my dot() function returned something, for example, another Foo?

class Foo(val count: Int)

fun Foo {
    return Foo(count + 1)

then, of course, it’s result is used to call whatever comes after the dot:


This prints 2, because the dot() function returned a new Foo with an increased counter.

As you can see, the dot operator gives us a lot of power and addresses most of the issues previously tackled only by aspect-oriented programming.

Flavors of the Dot

The real power of the dot operator comes in when you declare it with a parameter:

fun Dot) {

The parameter must be of the Dot type, of which there are a few interesting predefined values:


These values correspond, obviously, to the position of the dot:

fun test() {

One might think that in this example dot() is called three times: one for “a.b”, with the argument BOTTOM, then twice for “1..2”: first with LEFT, and then with RIGHT (these are not two BOTTOMs, because “..” is a single token in Kotlin), but in fact it gets called four times, and the fourth time (in fact it comes first) with TOP as an argument.

I’m sure you already see why: in Kotlin, we never forget to dot out i’s, and that dot counts as well; its position is clearly TOP (we could introduce a separate tittle() function, but we found it too inconvenient). Tittles above j’s count just as well, same for dots in ; ! ? etc.

The Depth of the Dot

You may be wondering what happens if dot() is defined like this:

fun {

There is a dot after this, which has type Foo, in the body of function itself, so dot() should be called recursively at that point and, seemingly, never terminate. This is called a higher-order dot, and is executed only if there’s a function dot1() defined on Foo. If dot1(), in turn, contains a higher-order dot, then dot2() is called and so on:

fun Foo.dot1() {
    println(this.count) // a call to dot2() if that is defined

This corresponds to Russel’s approach to set theory called type theory (with its notion of a class), which lies the solid foundation for statically-typed object-oriented programming.


We are planning to support the dot operator very soon. The first version will be restricted to basic ASCII characters such as . : ; ! ? and, of course i, but in the future we plan to expand it to other characters like ё.

Have a nice Dot!

Comments below can no longer be edited.

20 Responses to The Dot Operator

  1. Anton says:

    April 1, 2013

    😀 at ё

  2. MuppetGate says:

    April 1, 2013


    Nice try!

  3. Ladislav Thon says:

    April 1, 2013

    So the dot covers the “programmable semicolon” case and more, right? And we could make an entire program out of dots, right? This is so awesome! But… can we get a little more pointless?

    • Andrey Breslav says:

      April 1, 2013

      Three dots in a row don’t parse in Kotlin (yet). But thanks for pointing an important case out.

      • Paul says:

        April 1, 2013

        What if i want smth like “.:!?::.” or Kotlin doesn’t parse any symbols with dots if there is more then 2 of them? But in this case I can’t even use cool variables like iii (I prefer not i-j-k in my cycles, but i-ii-iii style…)

  4. Andrey Breslav says:

    April 1, 2013

    “.:!?::.” is not a single token, but a sequence of tokens, .dot() will be called according to the position of a dot in every token.

  5. Ian Clarke says:

    April 1, 2013

    Can we have something similar for whitespace?

  6. Simon says:

    April 1, 2013

    What value of Dot type will be used if I have Spanish-style string in my code
    String s = “¡Viva la Gloria!”
    The upside-down exclamation mark has the dot which is 100% lower than “i”‘s dot
    It is located practically at the CENTER.
    To my mind predefined values of Dot type are insufficient.
    Probably dot function should take double a and r which are angle and radius of the dot in polar coordinate system.

    • Andrey Breslav says:

      April 1, 2013

      Only the relative location inside the character matters, so “¡” gets a dot at the TOP

    • Andrey Breslav says:

      April 1, 2013

      I think that accepting Double in dot() will be too confusing for the users

  7. Simon says:

    April 1, 2013

    Oh, now I think I don’t understand clearly which dots count, and may be dots in string won’t count and my example is not correct
    But the question is still actual.

    • Andrey Breslav says:

      April 1, 2013

      Dots in a string are not supported yet, but they will surely be supported one day

  8. Alexander says:

    April 2, 2013

    I got my first WTF only in the middle of the article =)

  9. Guangyu HE says:

    April 1, 2014

    What’s the meaning of “the fourth time (in fact it comes first) with TOP as an argument.”? Would you have a detail explantation?

    • Andrey Breslav says:

      April 1, 2014

      To give you a hint, there’re are seven dots in the TOP position in this sentense. )))

  10. Guangyu HE says:

    April 2, 2014

    fun Dot) {
    println(“a dot!”)

    compiling the above code , I got the following error:
    Unresolved reference: Dot

    I code with Android Studio 0.5.3, kotlin-plugin: 0.7.271

  11. Stan says:

    August 29, 2014

    To be honest I don’t like it. At least from the first glance. I would say that this dot convention introduces new puzzlers. You can look at code and expect it to do one thing but in fact it will do another.

    • Andrey Breslav says:

      August 29, 2014

      Ok, I’ve put up an April Fools’ warning at the top of this post.