can anyone please explain the following behavior ...

# getting-started

[kartikpatodi]

can anyone please explain the following behavior

class A1(private val x: Int) {
    private val y: Int = 0
}

generates this code in Java

public final class A1 {
    private final int y;
    private final int x;

    public A1(int x) {
        this.x = x;
    }
}

while

class A2(private val x: Int) {
    private val y: Int
    init {
        y = 0
    }
}

generates

public final class A2 {
    private final int y;
    private final int x;

    public A2(int x) {
        this.x = x;
        this.y = 0;
    }
}

Why if init block y=0 is in constructor of A2 and not otherwise in case of A1?

[marstran]

Use backtics ``` instead of ''' to format the code.

[kartikpatodi]

edited

[Mike]

init in Kotlin is part of the construction process for a class, hence the code being emitted in the constructor.

In your simple example, you could obviously just assign 0 to y when you define it.

Help?

[kartikpatodi]

@Mike ok so does both express same behaviour?

[kartikpatodi]

also I experimented a bit and

class A1(private val x: Int) {
    private val y: Int = 2
}

generates

public final class A1 {
   private final int y;
   private final int x;

   public A1(int x) {
      this.x = x;
      this.y = 2;
   }
}

Which means it is omitting the constructor assignment only in the case of default values is supplied like 0 for Int
Which seems reasonable but if someone can confirm this.

[karelpeeters]

What's the problem? It doesn't matter whether the = 0 is generated, right?

[Mike]

I suspect they want to better understand what gets generated, so they're digging in. As to why, only they can answer that.

[kartikpatodi]

@Mike Actually was converting some legacy java code and did not understand the reason for the behavior, but now I gotit I think..