DevScrolls
48. What's the output?
console.log(3 + 4 + '5');
console.log(3 + 4 + '5');
Answer: B
Operator associativity is the order in which the compiler evaluates the expressions, either left-to-right or right-to-left. This only happens if all operators have the same precedence. We only have one type of operator: +. For addition, the associativity is left-to-right.
3 + 4 gets evaluated first. This results in the number 7.
7 + '5' results in "75" because of coercion. JavaScript converts the number 7 into a string, see question 15. We can concatenate two strings using the +operator. "7" + "5" results in "75".
Operator associativity is the order in which the compiler evaluates the expressions, either left-to-right or right-to-left. This only happens if all operators have the same precedence. We only have one type of operator: +. For addition, the associativity is left-to-right.
3 + 4 gets evaluated first. This results in the number 7.
7 + '5' results in "75" because of coercion. JavaScript converts the number 7 into a string, see question 15. We can concatenate two strings using the +operator. "7" + "5" results in "75".
49. What's the value of num?
const num = parseInt('7*6', 10);
const num = parseInt('7*6', 10);
Anonymous Poll
34%
A: 42
20%
B: "42"
6%
C: 7
40%
D: NaN
DevScrolls
49. What's the value of num?
const num = parseInt('7*6', 10);
const num = parseInt('7*6', 10);
Answer: C
Only the first numbers in the string is returned. Based on the radix (the second argument in order to specify what type of number we want to parse it to: base 10, hexadecimal, octal, binary, etc.), the parseInt checks whether the characters in the string are valid. Once it encounters a character that isn't a valid number in the radix, it stops parsing and ignores the following characters.
* is not a valid number. It only parses "7" into the decimal 7. num now holds the value of 7.
Only the first numbers in the string is returned. Based on the radix (the second argument in order to specify what type of number we want to parse it to: base 10, hexadecimal, octal, binary, etc.), the parseInt checks whether the characters in the string are valid. Once it encounters a character that isn't a valid number in the radix, it stops parsing and ignores the following characters.
* is not a valid number. It only parses "7" into the decimal 7. num now holds the value of 7.
50. What's the output?
[1, 2, 3].map(num => { if (typeof num === 'number') return; return num * 2; });
[1, 2, 3].map(num => { if (typeof num === 'number') return; return num * 2; });
Anonymous Poll
33%
A: []
33%
B: [null, null, null]
29%
C: [undefined, undefined, undefined]
5%
D: [ 3 x empty ]
👍2
DevScrolls
50. What's the output?
[1, 2, 3].map(num => { if (typeof num === 'number') return; return num * 2; });
[1, 2, 3].map(num => { if (typeof num === 'number') return; return num * 2; });
Answer: C
When mapping over the array, the value of num is equal to the element it’s currently looping over. In this case, the elements are numbers, so the condition of the if statement typeof num === "number" returns true. The map function creates a new array and inserts the values returned from the function.
However, we don’t return a value. When we don’t return a value from the function, the function returns undefined. For every element in the array, the function block gets called, so for each element we return undefined.
When mapping over the array, the value of num is equal to the element it’s currently looping over. In this case, the elements are numbers, so the condition of the if statement typeof num === "number" returns true. The map function creates a new array and inserts the values returned from the function.
However, we don’t return a value. When we don’t return a value from the function, the function returns undefined. For every element in the array, the function block gets called, so for each element we return undefined.
51. What's the output?
function getInfo(member, year) {
member.name = 'Lydia';
year = '1998';
}
const person = {
name: 'Sarah'
};
const birthYear = '1997';
getInfo(person, birthYear);
console.log(person, birthYear);
DevScrolls
51. What's the output? function getInfo(member, year) { member.name = 'Lydia'; year = '1998'; } const person = { name: 'Sarah' }; const birthYear = '1997'; getInfo(person, birthYear); console.log(person, birthYear);
DevScrolls
Output?
Answer: A
Arguments are passed by value, unless their value is an object, then they're passed by reference. birthYear is passed by value, since it's a string, not an object. When we pass arguments by value, a copy of that value is created (see question 46).
The variable birthYear has a reference to the value "1997". The argument year also has a reference to the value "1997", but it's not the same value as birthYear has a reference to. When we update the value of year by setting year equal to "1998", we are only updating the value of year. birthYear is still equal to "1997".
The value of person is an object. The argument member has a (copied) reference to the same object. When we modify a property of the object member has a reference to, the value of person will also be modified, since they both have a reference to the same object. person's name property is now equal to the value "Lydia"
Arguments are passed by value, unless their value is an object, then they're passed by reference. birthYear is passed by value, since it's a string, not an object. When we pass arguments by value, a copy of that value is created (see question 46).
The variable birthYear has a reference to the value "1997". The argument year also has a reference to the value "1997", but it's not the same value as birthYear has a reference to. When we update the value of year by setting year equal to "1998", we are only updating the value of year. birthYear is still equal to "1997".
The value of person is an object. The argument member has a (copied) reference to the same object. When we modify a property of the object member has a reference to, the value of person will also be modified, since they both have a reference to the same object. person's name property is now equal to the value "Lydia"
52. What's the output?
function greeting() {
throw 'Hello world!';
}
function sayHi() {
try {
const data = greeting(); console.log('It worked!', data);
} catch (e) {
console.log('Oh no an error:', e);
}
}
sayHi();
DevScrolls
52. What's the output? function greeting() { throw 'Hello world!'; } function sayHi() { try { const data = greeting(); console.log('It worked!', data); } catch (e) { console.log('Oh no an error:', e); } } sayHi();
DevScrolls
52. What's the output? function greeting() { throw 'Hello world!'; } function sayHi() { try { const data = greeting(); console.log('It worked!', data); } catch (e) { console.log('Oh no an error:', e); } } sayHi();
Answer: D
With the throw statement, we can create custom errors. With this statement, you can throw exceptions. An exception can be a string, a number, a boolean or an object. In this case, our exception is the string 'Hello world!'.
With the catch statement, we can specify what to do if an exception is thrown in the try block. An exception is thrown: the string 'Hello world!'. e is now equal to that string, which we log. This results in 'Oh an error: Hello world!'.
With the throw statement, we can create custom errors. With this statement, you can throw exceptions. An exception can be a string, a number, a boolean or an object. In this case, our exception is the string 'Hello world!'.
With the catch statement, we can specify what to do if an exception is thrown in the try block. An exception is thrown: the string 'Hello world!'. e is now equal to that string, which we log. This results in 'Oh an error: Hello world!'.
53. What's the output?
A: "Lamborghini"
B: "Maserati"
C: ReferenceError
D: TypeError
function Car() {
this.make = 'Lamborghini'; return {
make: 'Maserati'
};
}
const myCar = new Car(); console.log(myCar.make);A: "Lamborghini"
B: "Maserati"
C: ReferenceError
D: TypeError
https://thedailyfrontend.com/how-to-think-like-a-frontend-developer/
How to think like a Frontend Developer
How to think like a Frontend Developer
The Daily Frontend
How to think like a Frontend Developer - The Daily Frontend
To think like a frontend developer, you should focus on the following areas are User experience, Browser compatibility, Accessibility etc.
DevScrolls
https://thedailyfrontend.com/how-to-think-like-a-frontend-developer/ How to think like a Frontend Developer
This article is written with the help of Chat GPT 😃 Read this article and it it's helpful then plz comment to improve and publish more articles.✌️
👍1
DevScrolls
Output?
Answer: B
When you return a property, the value of the property is equal to the returned value, not the value set in the constructor function. We return the string "Maserati", so myCar.make is equal to "Maserati".
When you return a property, the value of the property is equal to the returned value, not the value set in the constructor function. We return the string "Maserati", so myCar.make is equal to "Maserati".
54. What's the output?
(() => { let x = (y = 10); })(); console.log(typeof x); console.log(typeof y);
(() => { let x = (y = 10); })(); console.log(typeof x); console.log(typeof y);
Anonymous Poll
71%
A: "undefined", "number"
21%
B: "number", "number"
0%
C: "object", "number"
7%
D: "number", "undefined"
DevScrolls
54. What's the output?
(() => { let x = (y = 10); })(); console.log(typeof x); console.log(typeof y);
(() => { let x = (y = 10); })(); console.log(typeof x); console.log(typeof y);
Answer: A
let x = (y = 10); is actually shorthand for:
When we set y equal to 10, we actually add a property y to the global object (window in browser, global in Node). In a browser, window.y is now equal to 10.
Then, we declare a variable x with the value of y, which is 10. Variables declared with the let keyword are block scoped, they are only defined within the block they're declared in; the immediately invoked function expression (IIFE) in this case. When we use the typeof operator, the operand x is not defined: we are trying to access x outside of the block it's declared in. This means that x is not defined. Values who haven't been assigned a value or declared are of type "undefined". console.log(typeof x) returns "undefined".
However, we created a global variable y when setting y equal to 10. This value is accessible anywhere in our code. y is defined, and holds a value of type "number". console.log(typeof y) returns "number".
let x = (y = 10); is actually shorthand for:
y = 10; let x = y;When we set y equal to 10, we actually add a property y to the global object (window in browser, global in Node). In a browser, window.y is now equal to 10.
Then, we declare a variable x with the value of y, which is 10. Variables declared with the let keyword are block scoped, they are only defined within the block they're declared in; the immediately invoked function expression (IIFE) in this case. When we use the typeof operator, the operand x is not defined: we are trying to access x outside of the block it's declared in. This means that x is not defined. Values who haven't been assigned a value or declared are of type "undefined". console.log(typeof x) returns "undefined".
However, we created a global variable y when setting y equal to 10. This value is accessible anywhere in our code. y is defined, and holds a value of type "number". console.log(typeof y) returns "number".
55. What's the output?
};
const pet = new Dog('Mara');
pet.bark();
delete Dog.prototype.bark; pet.bark();
class Dog {
constructor(name) {
this.name = name;
}
}
Dog.prototype.bark = function() {
console.log(Woof I am ${this.name});};
const pet = new Dog('Mara');
pet.bark();
delete Dog.prototype.bark; pet.bark();
DevScrolls
55. What's the output? class Dog { constructor(name) { this.name = name; } } Dog.prototype.bark = function() { console.log(Woof I am ${this.name}); }; const pet = new Dog('Mara'); pet.bark(); delete Dog.prototype.bark; pet.bark();