Javascript object members that are prototyped as arrays become shared by all class instances

前端 未结 3 800
日久生厌
日久生厌 2020-11-22 08:40

Has anyone noticed this behavior before? This really threw me off... I would have expected prototyped arrays to be private to each class instance rather than shared between

3条回答
  •  执笔经年
    2020-11-22 09:19

    The prototype of an object is just an object. The prototype properties are shared between all objects that inherit from that object. No copies of the properties are made if you create a new instance of a "class" (classes don't exist anyway in JS), i.e. an object which inherits from the prototype.

    It only makes a difference on how you use the these inherited properties:

    function Foo() {}
    
    Foo.prototype = {
        array: [],
        func: function() {}
    }
    
    a = new Foo();
    b = new Foo();
    
    a.array.push('bar');
    console.log(b.array); // prints ["bar"]
    
    b.func.bar = 'baz';
    console.log(a.func.bar); // prints baz
    

    In all these cases you are always working with the same object.

    But if you assign a value to a property of the object, the property will be set/created on the object itself, not its prototype, and hence is not shared:

    console.log(a.hasOwnProperty('array')); // prints false
    console.log(a.array); // prints ["bar"]
    a.array = ['foo'];
    console.log(a.hasOwnProperty('array')); // prints true
    console.log(a.array); // prints ["foo"]
    console.log(b.array); // prints ["bar"]
    

    If you want to create own arrays for each instance, you have to define it in the constructor:

    function Foo() {
        this.array = [];
    }
    

    because here, this refers to the new object that is generated when you call new Foo().

    The rule of thumb is: Instance-specific data should be assigned to the instance inside the constructor, shared data (like methods) should be assigned to the prototype.


    You might want to read Details of the object model which describes differences between class-based vs. prototype-based languages and how objects actually work.

    Update:

    You can access the prototype of an object via Object.getPrototypeOf(obj) (might not work in very old browsers), and Object.getPrototypeOf(a) === Object.getPrototypeOf(b) gives you true. It is the same object, also known as Foo.prototype.

提交回复
热议问题