Hey guys, style-wise, do you think there is anything “wrong” with a secondary copy-constructor, like...

# codereview

[Andrew Simpson]

Hey guys, style-wise, do you think there is anything “wrong” with a secondary copy-constructor, like:

class Person {

  constructor(id: Int, name: String)  

  constructor(person: Person) : this(person.id, person.name)

}

or would it be “more kotlin-like” to do something like a fun copy() = Person(id, name) method?

[Zun]

https://kotlinlang.org/docs/data-classes.html#copying

[Andrew Simpson]

I am not talking about data classes, this is a regular class, and I also am implementing deep copying of lists, which seems to not be consistent with .copy() from data class

[czuckie]

my preference would be to have a fun copy() but only because I enjoy class Clazz(val fields: Int, val that: Boolean, val go: String, val here: Short)