Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Kotlin thread safe native lazy singleton with parameter

In java we can write thead-safe singletons using double Checked Locking & volatile:

    public class Singleton {         private static volatile Singleton instance;          public static Singleton getInstance(String arg) {         Singleton localInstance = instance;         if (localInstance == null) {             synchronized (Singleton.class) {                 localInstance = instance;                 if (localInstance == null) {                     instance = localInstance = new Singleton(arg);                 }             }         }         return localInstance;     } } 

How we can write it in kotlin?


About object

object A {     object B {}     object C {}     init {         C.hashCode()     } } 

I used kotlin decompiler to get that

public final class A {    public static final A INSTANCE;     private A() {       INSTANCE = (A)this;       A.C.INSTANCE.hashCode();    }    static {       new A();    }     public static final class B {       public static final A.B INSTANCE;       private B() {          INSTANCE = (A.B)this;       }       static {          new A.B();       }    }     public static final class C {       public static final A.C INSTANCE;       private C() {          INSTANCE = (A.C)this;       }       static {          new A.C();       }    } } 

All of object have constructor invoke in static block. Based on it, we can think that it's not lazy.

Сlose to the right answer.

    class Singleton {         companion object {             val instance: Singleton by lazy(LazyThreadSafetyMode.PUBLICATION) { Singleton() }         }     } 

Decompiled:

public static final class Companion {       // $FF: synthetic field       private static final KProperty[] $$delegatedProperties = new KProperty[]{(KProperty)Reflection.property1(new PropertyReference1Impl(Reflection.getOrCreateKotlinClass(Singleton.Companion.class), "instance", "getInstance()Lru/example/project/tech/Singleton;"))};        @NotNull       public final Singleton getInstance() {          Lazy var1 = Singleton.instance$delegate;          KProperty var3 = $$delegatedProperties[0];          return (Singleton)var1.getValue();       }        private Companion() {       }        // $FF: synthetic method       public Companion(DefaultConstructorMarker $constructor_marker) {          this();       }    } 

I hope Kotlin developers will make non reflection implementation in future...

like image 686
punksta Avatar asked Feb 23 '16 20:02

punksta


People also ask

Are Kotlin singletons thread-safe?

The singleton initialization will be lazy and thread-safe. It's just an optimization to free some memory by setting the creator to null after initialization is complete.

Is lazy singleton thread-safe?

Lazy initialization is possible. It is also thread safe.

Is eager initialization singleton thread-safe?

It is thread-safe even if we remove final from public static final Singleton instance = new Singleton (); . That's because the JVM guarantees that the instance will be created before any thread access the static instance variable.

What is @singleton in Kotlin?

Using Singletons in Kotlin. By using the keyword object in your app, you're defining a singleton. A singleton is a design pattern in which a given class has only one single instance inside the entire app.


2 Answers

Kotlin has an equivalent of your Java code, but more safe. Your double lock check is not recommended even for Java. In Java you should use an inner class on the static which is also explained in Initialization-on-demand holder idiom.

But that's Java. In Kotlin, simply use an object (and optionally a lazy delegate):

object Singletons {     val something: OfMyType by lazy() { ... }      val somethingLazyButLessSo: OtherType = OtherType()     val moreLazies: FancyType by lazy() { ... } } 

You can then access any member variable:

// Singletons is lazy instantiated now, then something is lazy instantiated after.   val thing = Singletons.something // This is Doubly Lazy!  // this one is already loaded due to previous line val eager = Singletons.somethingLazyButLessSo  // and Singletons.moreLazies isn't loaded yet until first access... 

Kotlin intentionally avoids the confusion people have with singletons in Java. And avoids the "wrong versions" of this pattern -- of which there are many. It instead provides the simpler and the safest form of singletons.

Given the use of lazy(), if you have other members each would individually be lazy. And since they are initialized in the lambda passed to lazy() you can do things that you were asking about for about customizing the constructor, and for each member property.

As a result you have lazy loading of Singletons object (on first access of instance), and then lazier loading of something (on first access of member), and complete flexibility in object construction.

See also:

  • lazy() function
  • Lazy thread safe mode options
  • Object declarations

As a side note, look at object registry type libraries for Kotlin that are similar to dependency injection, giving you singletons with injection options:

  • Injekt - I'm the author
  • Kodein - Very similar and good
like image 59
7 revs, 2 users 99% Avatar answered Sep 30 '22 06:09

7 revs, 2 users 99%


Object declaration is exactly for this purpose:

object Singleton {     //singleton members } 

It is lazy and thread-safe, it initializes upon first call, much as Java's static initializers.

You can declare an object at top level or inside a class or another object.

For more info about working with objects from Java, please refer to this answer.


As to the parameter, if you want to achieve exactly the same semantics (first call to getInstance takes its argument to initialize the singleton, following calls just return the instance, dropping the arguments), I would suggest this construct:
private object SingletonInit { //invisible outside the file     lateinit var arg0: String }  object Singleton {     val arg0: String = SingletonInit.arg0 }  fun Singleton(arg0: String): Singleton { //mimic a constructor, if you want     synchronized(SingletonInit) {         SingletonInit.arg0 = arg0         return Singleton     } } 

The main flaw of this solution is that it requires the singleton to be defined in a separate file to hide the object SingletonInit, and you cannot reference Singleton directly until it's initialized.

Also, see a similar question about providing arguments to a singleton.

like image 39
hotkey Avatar answered Sep 30 '22 06:09

hotkey