It uses it in a strictly boolean sense, which I'll allow. What isn't allowed is the loose/early-return way JS can use &&; a contrived example that would not pass hard mode:
&&
const fizzbuzz = n => (n % 3 && (n % 5 && n || "Buzz")) || (n % 5 && "Fizz" || "FizzBuzz")
(an easy litmus test: does changing the order of the && expression change the result?)
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It uses it in a strictly boolean sense, which I'll allow. What isn't allowed is the loose/early-return way JS can use
&&; a contrived example that would not pass hard mode:(an easy litmus test: does changing the order of the
&&expression change the result?)