Hi, Uros.
Yes, I’m referring to the fact that arrow functions don’t have a separate this. You can create a closure with an arrow function, but arrow functions don’t have a separate lexical identifier* defined as you can see from the fact that this and arguments are not available inside an arrow function (if you try to access them it’ll fall back to the parent’s scope).
Perhaps the phrase “they don’t have their own lexical scope” is not the best choice, as they create a closure. In that sense they do have a lexical scope, it’s just not possible to reference it (for example assigning this to some other variable and passing it around).
The book “You Don’t Know JS Yet: ES.Next & Beyond” (Version 1 is available for now) is a great read that covers this topic.
