JavaScript Interview Questions
  • JavaScript Interview Questions
  • Contact
  • Introduction
  • Question 1
  • Question 2
  • Question 3
  • Question 4
  • Question 5
  • Question 6
  • Question 7
  • Question 8
  • Question 9
  • Question 10
  • Question 11
  • Question 12
  • Question 13
  • Question 14
  • Question 15
  • Question 16
  • Question 17
  • Question 18
  • Question 19
  • Question 20
  • Question 21
  • Question 22
  • Question 23
  • Question 24
  • Question 25
  • Question 26
  • Question 27
  • Question 28
  • Question 29
  • Question 30
  • Question 31
  • Question 32
  • Question 33
  • Question 34
  • Question 35
  • Question 36
  • Question 37
  • Question 38
  • Question 39
  • Question 40
  • Question 41
  • Question 42
  • Question 43
  • Question 44
  • Question 45
  • Question 46
  • Question 47
  • Question 48
  • Question 49
  • Question 50
  • Question 51
  • Question 52
  • Question 53
  • Question 54
  • Question 55
  • Question 56
  • Question 57
  • Question 58
  • Question 59
  • Question 60
  • Question 61
  • Question 62
  • Question 63
  • Question 64
  • Question 65
  • Question 66
  • Question 67
  • Question 68
  • Question 69
  • Question 70
  • Question 71
  • Question 72
  • Question 73
  • Question 74
  • Question 75
  • Question 76
  • Question 77
  • Question 78
  • Question 79
  • Question 80
  • Question 81
  • Question 82
  • Question 83
  • Question 84
  • Question 85
  • Question 86
  • Question 87
  • Question 88
  • Question 89
  • Question 90
  • Question 91
  • Question 92
  • Question 93
  • Question 94
  • Question 95
  • Question 96
  • Question 97
  • Question 98
  • Question 99
  • Question 100
  • Epilogue
Powered by GitBook
On this page
  • Question
  • Answer

Question 51

Question

Explain how to use WeakMap for private data storage in ES6 classes.

Answer

WeakMap is a fantastic tool for achieving private data storage within ES6 classes because it avoids memory leaks and offers controlled access to internal state.

Here's a breakdown of how it works:

  1. Understanding WeakMap:

    • A WeakMap stores key-value pairs where the keys must be objects, but the values can be any type.

    • Crucially, a WeakMap weakly references its keys. This means that if the object used as a key becomes unreachable (no other references to it exist), the corresponding entry in the WeakMap will automatically be garbage collected.

  2. Implementing Private Data with WeakMap:

    class MyClass {
      constructor() {
        this._data = new WeakMap(); // Create a private WeakMap
      }
    
      setData(key, value) {
        this._data.set(this, value); // Set data associated with this instance
      }
    
      getData(key) {
        return this._data.get(this, key);  // Retrieve data associated with this instance
      }
    }
    
    const myInstance = new MyClass();
    myInstance.setData('name', 'Alice'); // Set private data 
    console.log(myInstance.getData('name')); // Access private data

Explanation:

  • We create a WeakMap instance (_data) within the constructor of our class. This map will store private data associated with each individual instance of MyClass.

  • setData() sets key-value pairs in the _data map, using the current this object (the instance) as the key.

  • getData() retrieves values from the _data map based on the provided key and the current instance (this).

Why Use WeakMap?

  • Memory Safety: Because WeakMap uses weak references, if an instance of MyClass is no longer referenced anywhere else in your code, its data will be automatically cleaned up by the garbage collector. This prevents memory leaks.

  • Encapsulation: It effectively hides internal state from external access, promoting better encapsulation and data protection within your class.

PreviousQuestion 50NextQuestion 52

Last updated 9 months ago