Answer & Solution
let declarations are hoisted to the top of their block scope but are not initialized until the declaration is evaluated.
let declarations?
let declarations are hoisted to the top of their block scope but are not initialized until the declaration is evaluated.
What is the advantage of using let over var?
A). let allows for function scoping
B). let does not get hoisted
C). let avoids issues related to the temporal dead zone
D). let is globally scoped
What will be the output of the following code?
console.log(a); let a = 10;
A). undefined
B). 10
C). null
D). ReferenceError
In which scope are let variables hoisted?
A). Function scope
B). Block scope
C). Global scope
D). Module scope
What is the scope of a variable declared with let inside a loop?
A). Global scope
B). Function scope
C). Block scope
D). Module scope
What happens when you try to re-declare a let variable in the same scope?
A). It reassigns the value
B). It throws a SyntaxError
C). It re-declares the variable
D). It throws a TypeError
What is the 'temporal dead zone'?
A). The period during which a variable is declared but not yet initialized
B). The time when the variable is accessible throughout the program
C). The period after variable initialization
D). None of the above
What will be the output of the following code?
let i = 50; { let i = 55; console.log(i); } console.log(i);
A). 50 50
B). 55 50
C). 50 55
D). ReferenceError
How can you avoid variable hoisting issues with let?
A). Declare variables at the bottom of the code
B). Use var instead
C). Declare variables at the top of their scope
D). Do not declare variables
What will be the output of the following code?
let c = 5; { let c = 10; console.log(c); }
A). 5
B). 10
C). ReferenceError
D). undefined
What will be the output of the following code?
let d; console.log(d); d = 15;
A). undefined
B). 15
C). null
D). ReferenceError