search
HomeWeb Front-endJS TutorialUnderstanding arrow functions
Understanding arrow functionsJun 16, 2020 am 09:41 AM
js

I used to feel that I already understood arrow functions very well, and it was impossible to be fooled again. But I encountered a very strange problem a few days ago. After worrying about it for a long time, I found that it was a pitfall caused by the arrow function. Therefore, there is this article~

Problem Description

For example, I have a base class Animal, which has a basic method sayName. Each subsequent subclass that inherits from it needs to implement the sayName method to prove its identity. The base class code implementation is very simple:

class Animal {
	sayName = () => {
		throw new Error('你应该自己实现这个方法');
  }
}

So now I have to inherit from the Animal base class to implement a Pig subclass. The implementation is also very simple:

class Pig extends Animal {
	sayName() {
		console.log('I am a Pig');
	}
}

Hey, is it so simple? ? Where is the pitfall? However, when you actually run it, you will find that the result is not as expected:

Understanding arrow functions

Hey, why is this happening? What exactly went wrong? Why can this short few lines of code report an error?

Discover the problem

After a lot of tossing, I finally found that it was a pitfall of the arrow function. We only need to change the sayName of the Animal base class to a normal function, or change the sayName of the Pig subclass to an arrow function to solve this problem. So, what exactly is going on with arrow functions?

Writing this, I suddenly remembered that I was once interviewed by an interviewer about this question! At that time, the interviewer asked about the difference between arrow functions, ordinary functions of the class, and bind functions in the constructor for classes. The answer was clear and logical at the time, but when it came to inheritance, everything turned upside down. So to answer the above question, let’s first answer the interview question.

What is the difference between arrow functions, ordinary functions, and the bind function in constructor?

In order to see this problem more intuitively, we can use babel’s code compilation results to Better to see the difference.

First we enter a simple piece of code

class A {
  	constructor() {
		this.b = this.b.bind(this);    	
    }
  
    a() {
    	console.log('a');
    }
	  b() {
    	console.log('b')
    }
    c = () => {
    	console.log('c')
    }
}

Let’s see what babel compiles into:

"use strict";

function _instanceof(left, right) { if (right != null && typeof Symbol !== "undefined" && right[Symbol.hasInstance]) { return !!right[Symbol.hasInstance](left); } else { return left instanceof right; } }

function _classCallCheck(instance, Constructor) { if (!_instanceof(instance, Constructor)) { throw new TypeError("Cannot call a class as a function"); } }

function _defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } }

function _createClass(Constructor, protoProps, staticProps) { if (protoProps) _defineProperties(Constructor.prototype, protoProps); if (staticProps) _defineProperties(Constructor, staticProps); return Constructor; }

function _defineProperty(obj, key, value) { if (key in obj) { Object.defineProperty(obj, key, { value: value, enumerable: true, configurable: true, writable: true }); } else { obj[key] = value; } return obj; }

var A = /*#__PURE__*/function () {
  function A() {
    _classCallCheck(this, A);

    _defineProperty(this, "c", function () {
      console.log(&#39;c&#39;);
    });

    this.b = this.b.bind(this);
  }

  _createClass(A, [{
    key: "a",
    value: function a() {
      console.log(&#39;a&#39;);
    }
  }, {
    key: "b",
    value: function b() {
      console.log(&#39;b&#39;);
    }
  }]);

  return A;
}();

Most of the compiled code is auxiliary functions , we can only look at part of the key points:

var A = /*#__PURE__*/function () {
  function A() {
    _classCallCheck(this, A);

    _defineProperty(this, "c", function () {
      console.log(&#39;c&#39;);
    });

    this.b = this.b.bind(this);
  }

  _createClass(A, [{
    key: "a",
    value: function a() {
      console.log(&#39;a&#39;);
    }
  }, {
    key: "b",
    value: function b() {
      console.log(&#39;b&#39;);
    }
  }]);

  return A;
}();

From the compiled results, we can see the differences between each other:

  • Ordinary functions: After babel compilation, Will be placed on the prototype of the function

  • The bind function in the constructor: After compilation, it will not only be placed in the prototype of the function, but also will be generated every time it is instantiated. Bind the variable of the current instance context (this.b = this.b.bind(this)).

  • Arrow function: After babel is compiled, each time it is instantiated, defineProperty will be called to bind the arrow function content to the current instance context.

Judging from the compiled results, for actual development, if you need to bind context, it is best to use arrow functions. Because using the bind method will not only generate a prototype function, but also generate an additional function for each instantiation.

Update

After reading Yu Tengjing’s comments, I learned something more essential.

class For methods and variables declared with = sign, they will be used as attributes of the instance, while for attributes declared without = sign, they will be placed on the prototype chain. For example,

class A {
    a() {
        
    }
    b = 2;
    c = () => {
    }
}

For this class, when instantiated, b and c will be used as attributes of the instance, while a is placed on the prototype chain.

So why is it implemented like this? In fact, we can see that this is mentioned in the tc39 specification: Field declarations

For instances where the equal sign declaration is written directly, it is actually the syntax of Field declarations, which is equivalent to directly declaring such an instance attribute.

Back to topic

After we solve the previous problem, let’s return to the topic. After understanding the compilation results of the arrow function of the class in actual compilation conditions, it is actually easier to understand our problem.

Q: Why does an execution problem occur when a subclass declares sayName using a normal function?

A: If a subclass declares sayName using a normal function, the sayName declared by the subclass will be placed on the prototype of the constructor. However, since the base class's sayName uses arrow functions, each instance will directly have a sayName variable. According to the access rules of JavaScript variables, the variable itself will be searched first, and if it cannot be found, it will be searched on the prototype chain. Therefore, when looking for sayName, we directly find the sayName function declared by the base class, and will not look for it on the prototype chain, so there is a problem.

Q: Why does the subclass use arrow function to declare sayName and there is no problem in execution?

A: When an es6 class is initialized, it will first execute the constructor of the base class, and then execute its own constructor. Therefore, after the base class is initialized, the arrow function sayName declared by the subclass overrides the base class's, so there is no problem in execution.

Summarize

I thought I knew arrow functions very well, but I was fooled. Sure enough, there is no end to learning! But I also have a deeper understanding of intra-class arrow functions.

But after being reminded by everyone in the comment area, I found that the problem is not actually caused by the arrow function. Variables declared with the = sign in the class belong to the syntax of Field declarations. For variables declared in this way, they will be directly mounted to the properties of the instance instead of being mounted to the prototype chain.

Recommended tutorial: "JS Tutorial"

The above is the detailed content of Understanding arrow functions. For more information, please follow other related articles on the PHP Chinese website!

Statement
This article is reproduced at:掘金社区. If there is any infringement, please contact admin@php.cn delete
如何使用JS和百度地图实现地图平移功能如何使用JS和百度地图实现地图平移功能Nov 21, 2023 am 10:00 AM

如何使用JS和百度地图实现地图平移功能百度地图是一款广泛使用的地图服务平台,在Web开发中经常用于展示地理信息、定位等功能。本文将介绍如何使用JS和百度地图API实现地图平移功能,并提供具体的代码示例。一、准备工作使用百度地图API前,首先需要在百度地图开放平台(http://lbsyun.baidu.com/)上申请一个开发者账号,并创建一个应用。创建完成

如何使用JS和百度地图实现地图多边形绘制功能如何使用JS和百度地图实现地图多边形绘制功能Nov 21, 2023 am 10:53 AM

如何使用JS和百度地图实现地图多边形绘制功能在现代网页开发中,地图应用已经成为常见的功能之一。而地图上绘制多边形,可以帮助我们将特定区域进行标记,方便用户进行查看和分析。本文将介绍如何使用JS和百度地图API实现地图多边形绘制功能,并提供具体的代码示例。首先,我们需要引入百度地图API。可以利用以下代码在HTML文件中导入百度地图API的JavaScript

js字符串转数组js字符串转数组Aug 03, 2023 pm 01:34 PM

js字符串转数组的方法:1、使用“split()”方法,可以根据指定的分隔符将字符串分割成数组元素;2、使用“Array.from()”方法,可以将可迭代对象或类数组对象转换成真正的数组;3、使用for循环遍历,将每个字符依次添加到数组中;4、使用“Array.split()”方法,通过调用“Array.prototype.forEach()”将一个字符串拆分成数组的快捷方式。

如何使用JS和百度地图实现地图热力图功能如何使用JS和百度地图实现地图热力图功能Nov 21, 2023 am 09:33 AM

如何使用JS和百度地图实现地图热力图功能简介:随着互联网和移动设备的迅速发展,地图成为了一种普遍的应用场景。而热力图作为一种可视化的展示方式,能够帮助我们更直观地了解数据的分布情况。本文将介绍如何使用JS和百度地图API来实现地图热力图的功能,并提供具体的代码示例。准备工作:在开始之前,你需要准备以下事项:一个百度开发者账号,并创建一个应用,获取到相应的AP

js中new操作符做了哪些事情js中new操作符做了哪些事情Nov 13, 2023 pm 04:05 PM

js中new操作符做了:1、创建一个空对象,这个新对象将成为函数的实例;2、将新对象的原型链接到构造函数的原型对象,这样新对象就可以访问构造函数原型对象中定义的属性和方法;3、将构造函数的作用域赋给新对象,这样新对象就可以通过this关键字来引用构造函数中的属性和方法;4、执行构造函数中的代码,构造函数中的代码将用于初始化新对象的属性和方法;5、如果构造函数中没有返回等等。

用JavaScript模拟实现打字小游戏!用JavaScript模拟实现打字小游戏!Aug 07, 2022 am 10:34 AM

这篇文章主要为大家详细介绍了js实现打字小游戏,文中示例代码介绍的非常详细,具有一定的参考价值,感兴趣的小伙伴们可以参考一下。

php可以读js内部的数组吗php可以读js内部的数组吗Jul 12, 2023 pm 03:41 PM

php在特定情况下可以读js内部的数组。其方法是:1、在JavaScript中,创建一个包含需要传递给PHP的数组的变量;2、使用Ajax技术将该数组发送给PHP脚本。可以使用原生的JavaScript代码或者使用基于Ajax的JavaScript库如jQuery等;3、在PHP脚本中,接收传递过来的数组数据,并进行相应的处理即可。

js是什么编程语言?js是什么编程语言?May 05, 2019 am 10:22 AM

js全称JavaScript,是一种具有函数优先的轻量级,直译式、解释型或即时编译型的高级编程语言,是一种属于网络的高级脚本语言;JavaScript基于原型编程、多范式的动态脚本语言,并且支持面向对象、命令式和声明式,如函数式编程。

See all articles

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

AI Hentai Generator

AI Hentai Generator

Generate AI Hentai for free.

Hot Article

R.E.P.O. Energy Crystals Explained and What They Do (Yellow Crystal)
2 weeks agoBy尊渡假赌尊渡假赌尊渡假赌
Repo: How To Revive Teammates
4 weeks agoBy尊渡假赌尊渡假赌尊渡假赌
Hello Kitty Island Adventure: How To Get Giant Seeds
4 weeks agoBy尊渡假赌尊渡假赌尊渡假赌

Hot Tools

Dreamweaver CS6

Dreamweaver CS6

Visual web development tools

SecLists

SecLists

SecLists is the ultimate security tester's companion. It is a collection of various types of lists that are frequently used during security assessments, all in one place. SecLists helps make security testing more efficient and productive by conveniently providing all the lists a security tester might need. List types include usernames, passwords, URLs, fuzzing payloads, sensitive data patterns, web shells, and more. The tester can simply pull this repository onto a new test machine and he will have access to every type of list he needs.

MantisBT

MantisBT

Mantis is an easy-to-deploy web-based defect tracking tool designed to aid in product defect tracking. It requires PHP, MySQL and a web server. Check out our demo and hosting services.

mPDF

mPDF

mPDF is a PHP library that can generate PDF files from UTF-8 encoded HTML. The original author, Ian Back, wrote mPDF to output PDF files "on the fly" from his website and handle different languages. It is slower than original scripts like HTML2FPDF and produces larger files when using Unicode fonts, but supports CSS styles etc. and has a lot of enhancements. Supports almost all languages, including RTL (Arabic and Hebrew) and CJK (Chinese, Japanese and Korean). Supports nested block-level elements (such as P, DIV),

ZendStudio 13.5.1 Mac

ZendStudio 13.5.1 Mac

Powerful PHP integrated development environment