Simple simulation of call, apply and bind methods in JavaScript

Hypocrisy and perfunctoriness 2021-04-16 13:51:17
simple simulation apply bind methods


Introduction

After reading 《 You don't know JavaScript-- Scroll up 》 About China this After the introduction and in-depth chapters of , about this The direction of I use this article to summarize . And then I wondered if I could use this Knowledge about , Simulate it javascript It's more commonly used in call、apply、bind Methods? ?

So there is this article , I don't want to talk much nonsense !

Implicit loss

Due to the use of implicit loss in Simulation Implementation , So I'd like to introduce .

Implicit loss is a common this Binding problem , Refer to : Functions that are implicitly bound lose bound objects , And eventually apply to the default binding . Talk is talk : It was an implicit binding (obj.xxx this Point to obj) In the end, the default binding is applied (this Point to global object ).

Common cases of implicit loss 1: reference

var a = 'window'
function foo() {
console.log(this.a)
}
var obj = {
a: 'obj',
foo: foo
}
obj.foo() // 'obj' here this => obj
var lose = obj.foo
lose() // 'window' here this => window

Common cases of implicit loss 2: Passed in as a callback function

var a = 'window'
function foo() {
console.log(this.a)
}
var obj = {
a: 'obj',
foo: foo
}
function lose(callback) {
callback()
}
lose(obj.foo) // 'window' here this => window
// ================ Split line ===============
var t = 'window'
function bar() {
console.log(this.t)
}
setTimeout(bar, 1000) // 'window'

For this, I conclude that ( I don't know right or wrong ): After excluding explicit binding , No matter how you do value passing , As long as it ends up being called without any modification , Then it applies to the default binding

Further get the key principle of the whole implementation : No matter how you do value passing , The way it's finally called determines this The direction of

Hard binding

The intuitive description of hard binding is : Once a function is explicitly specified this And then no matter how you call it later , its this The direction of will never be changed again

The implementation of hard binding solves the problem of implicit loss , bind The implementation of functions is based on the principle of hard binding

// Solve implicit loss
var a = 'window'
function foo() {
console.log(this.a)
}
var obj = {
a: 'obj',
foo: foo
}
function lose(callback) {
callback()
}
lose(obj.foo) // 'window'
var fixTheProblem = obj.foo.bind(obj)
lose(fixTheProblem) // 'obj'

Implementation and principle analysis

Simulation Implementation call

// Simulation Implementation call
Function.prototype._call = function ($this, ...parms) { // ...parms Now it's rest Operator , Used to receive all incoming arguments and return an array containing them
/*
this Will point to the call _call The function object of the method this It must be a function
** This step is crucial ** => Then temporarily store the object to our designated $this(context) In the object
*/
$this['caller'] = this
//$this['caller'](...parms)
// This writing will be clearer than the one above
$this.caller(...parms) // ...parms Now it's spread Operator , Used to deconstruct elements in an array to caller Functions pass in arguments
/*
For the sake of clarity , Use the following more explicit way of writing instead of commenting out
1. $this.caller It's about us changing this Point to the original function
2. But because it's now $this.caller call , The rules of implicit binding are applied
3. therefore this Success points to $this
*/
delete $this['caller'] // This is a temporary property and cannot destroy the original structure of the artificially bound object , So it needs to be deleted after use
}

Simulation Implementation apply

// Simulation Implementation apply ** And _call The implementation of is almost the same , The main difference is only in the method of parameter transmission / On type **
Function.prototype._apply = function ($this, parmsArr) { // According to the original apply The second parameter passes in an array
$this['caller'] = this
$this['caller'](...parmsArr) // ...parmsArr Now it's spread Operator , Used to deconstruct elements in an array to caller Functions pass in arguments
delete $this['caller']
}

since _call And _apply The previous similarity ( Coupling degree ) So high , Then we can further study them ( The same code for ) To withdraw

function interface4CallAndApply(caller, $this, parmsOrParmArr) {
$this['caller'] = caller
$this['caller'](...parmsOrParmArr)
delete $this['caller']
}
Function.prototype._call = function ($this, ...parms) {
var funcCaller = this
interface4CallAndApply(funcCaller, $this, parms)
}
Function.prototype._apply = function ($this, parmsArr) {
var funcCaller = this
interface4CallAndApply(funcCaller, $this, parmsArr)
}

One that I think can be better demonstrated _call and _apply Examples of implementation principles

var myName = 'window'
var obj = {
myName: 'Fitz',
sayName() {
console.log(this.myName)
}
}
var foo = obj.sayName
var bar = {
myName: 'bar',
foo
}
bar.foo()

Simulation Implementation bind

// Use the principle of hard binding to simulate the implementation bind
Function.prototype._bind = function ($this, ...parms) {
$bindCaller = this // Save the call _bind Object of function Be careful : The object is a function
// According to the original bind The return value of the function : It's a function
return function () { // use rest Operator substitution arguments To collect incoming arguments
return $bindCaller._apply($this, parms)
}
}

An example of how hard binding works

function hardBind(fn) {
var caller = this
var parms = [].slice.call(arguments, 1)
return function bound() {
parms = [...parms, ...arguments]
fn.apply(caller, parms) // apply You can accept a pseudo array instead of an array
}
}
var myName = 'window'
function foo() {
console.log(this.myName)
}
var obj = {
myName: 'obj',
foo: foo,
hardBind: hardBind
}
// Under normal circumstances
foo() // 'window'
obj.foo() // 'obj'
var hb = hardBind(foo)
// You can see that once hard bound, no matter how it is called in the end, it can't be changed this Point to
hb() // 'window'
obj.hb = hb // to obj Add this method to test
obj.hb() // 'window'
// Let's make an impression
var hb2 = obj.hardBind(foo)
hb2() // 'obj' // This call this It should have pointed to window

Overall implementation ( Pure version / No comment )

function interface4CallAndApply(caller, $this, parmsOrParmArr) {
$this['caller'] = caller
$this['caller'](...parmsOrParmArr)
delete $this['caller']
}
Function.prototype._call = function ($this, ...parms) {
var funcCaller = this
interface4CallAndApply(funcCaller, $this, parms)
}
Function.prototype._apply = function ($this, parmsArr) {
var funcCaller = this
interface4CallAndApply(funcCaller, $this, parmsArr)
}
Function.prototype._bind = function ($this, ...parms) {
$bindCaller = this
return function () {
return $bindCaller._apply($this, parms)
}
}
// ============ test ===============
var foo = {
name: 'foo',
sayHello: function (a, b) {
console.log(`hello, get the parms => ${a} and ${b}`)
}
}
var bar = {
name: 'bar'
}
foo.sayHello._call(bar, 'Fitz', 'smart')
foo.sayHello._apply(bar, ['Fitz', 'smart'])
var baz = foo.sayHello._bind(bar, 'Fitz', 'smart')
baz()
var testHardBind = foo.sayHello._bind(bar, 'hard', 'bind')
testHardBind._call(Object.create(null)) // hello, get the parms => hard and bind test _bind Hard binding of

At the end

I'm just a little white who is learning the front end , If there is something wrong, please correct it

If you feel inspired or helpful , Please leave a message or pay attention to me , Thank you very much! !

版权声明
本文为[Hypocrisy and perfunctoriness]所创,转载请带上原文链接,感谢
https://javamana.com/2021/04/20210416123922757p.html

  1. 【计算机网络 12(1),尚学堂马士兵Java视频教程
  2. 【程序猿历程,史上最全的Java面试题集锦在这里
  3. 【程序猿历程(1),Javaweb视频教程百度云
  4. Notes on MySQL 45 lectures (1-7)
  5. [computer network 12 (1), Shang Xuetang Ma soldier java video tutorial
  6. The most complete collection of Java interview questions in history is here
  7. [process of program ape (1), JavaWeb video tutorial, baidu cloud
  8. Notes on MySQL 45 lectures (1-7)
  9. 精进 Spring Boot 03:Spring Boot 的配置文件和配置管理,以及用三种方式读取配置文件
  10. Refined spring boot 03: spring boot configuration files and configuration management, and reading configuration files in three ways
  11. 精进 Spring Boot 03:Spring Boot 的配置文件和配置管理,以及用三种方式读取配置文件
  12. Refined spring boot 03: spring boot configuration files and configuration management, and reading configuration files in three ways
  13. 【递归,Java传智播客笔记
  14. [recursion, Java intelligence podcast notes
  15. [adhere to painting for 386 days] the beginning of spring of 24 solar terms
  16. K8S系列第八篇(Service、EndPoints以及高可用kubeadm部署)
  17. K8s Series Part 8 (service, endpoints and high availability kubeadm deployment)
  18. 【重识 HTML (3),350道Java面试真题分享
  19. 【重识 HTML (2),Java并发编程必会的多线程你竟然还不会
  20. 【重识 HTML (1),二本Java小菜鸟4面字节跳动被秒成渣渣
  21. [re recognize HTML (3) and share 350 real Java interview questions
  22. [re recognize HTML (2). Multithreading is a must for Java Concurrent Programming. How dare you not
  23. [re recognize HTML (1), two Java rookies' 4-sided bytes beat and become slag in seconds
  24. 造轮子系列之RPC 1:如何从零开始开发RPC框架
  25. RPC 1: how to develop RPC framework from scratch
  26. 造轮子系列之RPC 1:如何从零开始开发RPC框架
  27. RPC 1: how to develop RPC framework from scratch
  28. 一次性捋清楚吧,对乱糟糟的,Spring事务扩展机制
  29. 一文彻底弄懂如何选择抽象类还是接口,连续四年百度Java岗必问面试题
  30. Redis常用命令
  31. 一双拖鞋引发的血案,狂神说Java系列笔记
  32. 一、mysql基础安装
  33. 一位程序员的独白:尽管我一生坎坷,Java框架面试基础
  34. Clear it all at once. For the messy, spring transaction extension mechanism
  35. A thorough understanding of how to choose abstract classes or interfaces, baidu Java post must ask interview questions for four consecutive years
  36. Redis common commands
  37. A pair of slippers triggered the murder, crazy God said java series notes
  38. 1、 MySQL basic installation
  39. Monologue of a programmer: despite my ups and downs in my life, Java framework is the foundation of interview
  40. 【大厂面试】三面三问Spring循环依赖,请一定要把这篇看完(建议收藏)
  41. 一线互联网企业中,springboot入门项目
  42. 一篇文带你入门SSM框架Spring开发,帮你快速拿Offer
  43. 【面试资料】Java全集、微服务、大数据、数据结构与算法、机器学习知识最全总结,283页pdf
  44. 【leetcode刷题】24.数组中重复的数字——Java版
  45. 【leetcode刷题】23.对称二叉树——Java版
  46. 【leetcode刷题】22.二叉树的中序遍历——Java版
  47. 【leetcode刷题】21.三数之和——Java版
  48. 【leetcode刷题】20.最长回文子串——Java版
  49. 【leetcode刷题】19.回文链表——Java版
  50. 【leetcode刷题】18.反转链表——Java版
  51. 【leetcode刷题】17.相交链表——Java&python版
  52. 【leetcode刷题】16.环形链表——Java版
  53. 【leetcode刷题】15.汉明距离——Java版
  54. 【leetcode刷题】14.找到所有数组中消失的数字——Java版
  55. 【leetcode刷题】13.比特位计数——Java版
  56. oracle控制用户权限命令
  57. 三年Java开发,继阿里,鲁班二期Java架构师
  58. Oracle必须要启动的服务
  59. 万字长文!深入剖析HashMap,Java基础笔试题大全带答案
  60. 一问Kafka就心慌?我却凭着这份,图灵学院vip课程百度云