++ and decrement
--, which are commonly used with loops. These unary operators add or subtract a one from a number in a variable:
let i = 0; i++; // 0 i++; // 1 i--; // 2 i--; // 1
They can be used as a prefix and postfix:
let i = 0; ++i; // 1 ++i; // 2 --i; // 1 --i; // 0
It seems to be no difference between the postfix and prefix usages. And that's where it gets complicated.
Unlike other operators, which have no side-effects and simply return a new value, increment and decrement not only return a value but also change it.
If you use a prefix, the variable is changed first, and then it's returned.
If you use a postfix, it's the opposite: the variable is returned first, and then its value is changed
The rule works exactly the same for both incrementing and decrementing. For simplicity's sake, we'll only look at increments for now:
let x = 5; console.log(++x); // => 6 console.log(x); // => 6 console.log(x++); // => 6 console.log(x); // => 7
What's going on?
++xhas been printed. It's a prefix increment, so initially, the value increased by 1, and then the result was returned and printed
- Since the value changed,
- Now print
x++. It's a postfix increment, so it returns the value before it increments by 1
- Since the value changed,
It gets worse when increments are put into other operations:
x = i++ - 7 + --h. It's almost impossible to understand such code and writing it should be considered a serious crime.
- Never mix operations/functions without side effects with operations/functions with side effects within a single expression
- Use increment and decrement only if there is no difference between the prefix and postfix version. It should be separate from other expressions and on a separate line of code
Write a function,
makeItFunny(), which returns a copy of a string passed to it, where each nth element is uppercase. n also needs to be passed to the function.
To find each nth element, you will need to find the remainder from division
%. Think about how you can use it.
const text = 'I never look back'; // Every 3rd element makeItFunny(text, 3); // 'I NevEr LooK bAck'
The exercise doesn't pass checking. What to do? 😶
If you've reached a deadlock it's time to ask your question in the «Discussions». How ask a question correctly:
- Be sure to attach the test output, without it it's almost impossible to figure out what went wrong, even if you show your code. It's complicated for developers to execute code in their heads, but having a mistake before their eyes most probably will be helpful.
In my environment the code works, but not here 🤨
Tests are designed so that they test the solution in different ways and against different data. Often the solution works with one kind of input data but doesn't work with others. Check the «Tests» tab to figure this out, you can find hints at the error output.
My code is different from the teacher's one 🤔
It's fine. 🙆 One task in programming can be solved in many different ways. If your code passed all tests, it complies with the task conditions.
In some rare cases, the solution may be adjusted to the tests, but this can be seen immediately.
I've read the lessons but nothing is clear 🙄
It's hard to make educational materials that will suit everyone. We do our best but there is always something to improve. If you see a material that is not clear to you, describe the problem in “Discussions”. It will be great if you'll write unclear points in the question form. Usually, we need a few days for corrections.
By the way, you can participate in courses improvement. There is a link below to the lessons course code which you can edit right in your browser.