In programming, we often want to take something and extend it.
For instance, we have a user
object with its properties and methods, and want to make admin
and guest
as slightly modified variants of it. We’d like to reuse what we have in user
, not copy/reimplement its methods, just build a new object on top of it.
Prototypal inheritance is a language feature that helps in that.
[[Prototype]]
In JavaScript, objects have a special hidden property [[Prototype]]
(as named in the specification), that is either null
or references another object. That object is called “a prototype”:
When we read a property from object
, and it’s missing, JavaScript automatically takes it from the prototype. In programming, this is called “prototypal inheritance”. And soon we’ll study many examples of such inheritance, as well as cooler language features built upon it.
The property [[Prototype]]
is internal and hidden, but there are many ways to set it.
One of them is to use the special name __proto__
, like this:
let animal = {
eats: true
};
let rabbit = {
jumps: true
};
rabbit.__proto__ = animal; // sets rabbit.[[Prototype]] = animal
Now if we read a property from rabbit
, and it’s missing, JavaScript will automatically take it from animal
.
For instance:
let animal = {
eats: true
};
let rabbit = {
jumps: true
};
rabbit.__proto__ = animal; // (*)
// we can find both properties in rabbit now:
alert( rabbit.eats ); // true (**)
alert( rabbit.jumps ); // true
Here the line (*)
sets animal
to be the prototype of rabbit
.
Then, when alert
tries to read property rabbit.eats
(**)
, it’s not in rabbit
, so JavaScript follows the [[Prototype]]
reference and finds it in animal
(look from the bottom up):
Here we can say that “animal
is the prototype of rabbit
” or “rabbit
prototypically inherits from animal
”.
So if animal
has a lot of useful properties and methods, then they become automatically available in rabbit
. Such properties are called “inherited”.
If we have a method in animal
, it can be called on rabbit
:
let animal = {
eats: true,
walk() {
alert("Animal walk");
}
};
let rabbit = {
jumps: true,
__proto__: animal
};
// walk is taken from the prototype
rabbit.walk(); // Animal walk
The method is automatically taken from the prototype, like this:
The prototype chain can be longer:
let animal = {
eats: true,
walk() {
alert("Animal walk");
}
};
let rabbit = {
jumps: true,
__proto__: animal
};
let longEar = {
earLength: 10,
__proto__: rabbit
};
// walk is taken from the prototype chain
longEar.walk(); // Animal walk
alert(longEar.jumps); // true (from rabbit)
Now if we read something from longEar
, and it’s missing, JavaScript will look for it in rabbit
, and then in animal
.
There are only two limitations:
- The references can’t go in circles. JavaScript will throw an error if we try to assign
__proto__
in a circle. - The value of
__proto__
can be either an object ornull
. Other types are ignored.
Also it may be obvious, but still: there can be only one [[Prototype]]
. An object may not inherit from two others.
__proto__
is a historical getter/setter for [[Prototype]]
It’s a common mistake of novice developers not to know the difference between these two.
Please note that __proto__
is not the same as the internal [[Prototype]]
property. It’s a getter/setter for [[Prototype]]
. Later we’ll see situations where it matters, for now let’s just keep it in mind, as we build our understanding of JavaScript language.
The __proto__
property is a bit outdated. It exists for historical reasons, modern JavaScript suggests that we should use Object.getPrototypeOf/Object.setPrototypeOf
functions instead that get/set the prototype. We’ll also cover these functions later.
By the specification, __proto__
must only be supported by browsers. In fact though, all environments including server-side support __proto__
, so we’re quite safe using it.
As the __proto__
notation is a bit more intuitively obvious, we use it in the examples.
Writing doesn’t use prototype
The prototype is only used for reading properties.
Write/delete operations work directly with the object.
In the example below, we assign its own walk
method to rabbit
:
let animal = {
eats: true,
walk() {
/* this method won't be used by rabbit */
}
};
let rabbit = {
__proto__: animal
};
rabbit.walk = function() {
alert("Rabbit! Bounce-bounce!");
};
rabbit.walk(); // Rabbit! Bounce-bounce!
From now on, rabbit.walk()
call finds the method immediately in the object and executes it, without using the prototype:
Accessor properties are an exception, as assignment is handled by a setter function. So writing to such a property is actually the same as calling a function.
For that reason admin.fullName
works correctly in the code below:
let user = {
name: "John",
surname: "Smith",
set fullName(value) {
[this.name, this.surname] = value.split(" ");
},
get fullName() {
return `${this.name} ${this.surname}`;
}
};
let admin = {
__proto__: user,
isAdmin: true
};
alert(admin.fullName); // John Smith (*)
// setter triggers!
admin.fullName = "Alice Cooper"; // (**)
alert(admin.fullName); // Alice Cooper, state of admin modified
alert(user.fullName); // John Smith, state of user protected
Here in the line (*)
the property admin.fullName
has a getter in the prototype user
, so it is called. And in the line (**)
the property has a setter in the prototype, so it is called.
The value of “this”
An interesting question may arise in the example above: what’s the value of this
inside set fullName(value)
? Where are the properties this.name
and this.surname
written: into user
or admin
?
The answer is simple: this
is not affected by prototypes at all.
No matter where the method is found: in an object or its prototype. In a method call, this
is always the object before the dot.
So, the setter call admin.fullName=
uses admin
as this
, not user
.
That is actually a super-important thing, because we may have a big object with many methods, and have objects that inherit from it. And when the inheriting objects run the inherited methods, they will modify only their own states, not the state of the big object.
For instance, here animal
represents a “method storage”, and rabbit
makes use of it.
The call rabbit.sleep()
sets this.isSleeping
on the rabbit
object:
// animal has methods
let animal = {
walk() {
if (!this.isSleeping) {
alert(`I walk`);
}
},
sleep() {
this.isSleeping = true;
}
};
let rabbit = {
name: "White Rabbit",
__proto__: animal
};
// modifies rabbit.isSleeping
rabbit.sleep();
alert(rabbit.isSleeping); // true
alert(animal.isSleeping); // undefined (no such property in the prototype)
The resulting picture:
If we had other objects, like bird
, snake
, etc., inheriting from animal
, they would also gain access to methods of animal
. But this
in each method call would be the corresponding object, evaluated at the call-time (before dot), not animal
. So when we write data into this
, it is stored into these objects.
As a result, methods are shared, but the object state is not.
for…in loop
The for..in
loop iterates over inherited properties too.
For instance:
let animal = {
eats: true
};
let rabbit = {
jumps: true,
__proto__: animal
};
// Object.keys only returns own keys
alert(Object.keys(rabbit)); // jumps
// for..in loops over both own and inherited keys
for(let prop in rabbit) alert(prop); // jumps, then eats
If that’s not what we want, and we’d like to exclude inherited properties, there’s a built-in method obj.hasOwnProperty(key): it returns true
if obj
has its own (not inherited) property named key
.
So we can filter out inherited properties (or do something else with them):
let animal = {
eats: true
};
let rabbit = {
jumps: true,
__proto__: animal
};
for(let prop in rabbit) {
let isOwn = rabbit.hasOwnProperty(prop);
if (isOwn) {
alert(`Our: ${prop}`); // Our: jumps
} else {
alert(`Inherited: ${prop}`); // Inherited: eats
}
}
Here we have the following inheritance chain: rabbit
inherits from animal
, that inherits from Object.prototype
(because animal
is a literal object {...}
, so it’s by default), and then null
above it:
Note, there’s one funny thing. Where is the method rabbit.hasOwnProperty
coming from? We did not define it. Looking at the chain we can see that the method is provided by Object.prototype.hasOwnProperty
. In other words, it’s inherited.
…But why does hasOwnProperty
not appear in the for..in
loop like eats
and jumps
do, if for..in
lists inherited properties?
The answer is simple: it’s not enumerable. Just like all other properties of Object.prototype
, it has enumerable:false
flag. And for..in
only lists enumerable properties. That’s why it and the rest of the Object.prototype
properties are not listed.
Almost all other key/value-getting methods, such as Object.keys
, Object.values
and so on ignore inherited properties.
They only operate on the object itself. Properties from the prototype are not taken into account.
Summary
- In JavaScript, all objects have a hidden
[[Prototype]]
property that’s either another object ornull
. - We can use
obj.__proto__
to access it (a historical getter/setter, there are other ways, to be covered soon). - The object referenced by
[[Prototype]]
is called a “prototype”. - If we want to read a property of
obj
or call a method, and it doesn’t exist, then JavaScript tries to find it in the prototype. - Write/delete operations act directly on the object, they don’t use the prototype (assuming it’s a data property, not a setter).
- If we call
obj.method()
, and themethod
is taken from the prototype,this
still referencesobj
. So methods always work with the current object even if they are inherited. - The
for..in
loop iterates over both its own and its inherited properties. All other key/value-getting methods only operate on the object itself.
Comments are back :)
<code>
tag, for several lines – wrap them in<pre>
tag, for more than 10 lines – use a sandbox (plnkr, jsbin, codepen…)