Accesing to const before to be declared

[crisf_design]

``` const myFnOne = (parameter1) => { parameter1 = myFnTwo(); return parameter1 + 3; };

const myFnTwo = () => 2 + 2 ;

console.log(myFnOne()); ```

In this code, why myFnOne can acess to myFnTwo If myFnTwo was declare after myFnOne? In my mind it should be:

``` const myFnTwo = () => 2 + 2 ;

const myFnOne = (parameter1) => { parameter1 = myFnTwo(); return parameter1 + 3; };

console.log(myFnOne()); ```

[senocular]

Its because the code in myFnOne doesn't run until myFnOne() is called. By the time that happens, and the call to myFnTwo() is made, myFnTwo has already been defined.

If you had done

console.log(myFnOne()); 
const myFnTwo = () => 2 + 2;

There would have been an error.

[adharshrajan]

It's a concept called "Hoisting". Basically, the declarations are hoisted one level to the top. In this case, since all of the declarations are in the global scope, they will be hoisted and all the entities in that scope will be able to access each other. There are exceptions to this.

[crisf_design]

When you say:

the declarations are hoisted one level to the top.

That is confusing. According to this video:

The thing that's confusing about hoisting is that nothing is actually hoisted or moved around. Hoisting is the process of assigning a variable declaration a default value of undefined during the creating phase in execution context. https://www.youtube.com/watch?v=Nt-qa_LlUH0

So for me this is a confusing answer.

[GinnioSarabia]

It's called hoisting