Please some admin (or you, Loige) add the "[2018]" tag since this is well established in 2020. It was "emerging to already there" back in 2018.<p>I also missed generators from this list, which are the "official" (but a lot more complex than the ones showed here!) way of having multiple async returns:<p><a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/yield" rel="nofollow">https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...</a>
Returning an object and returning an array aren't exactly new concepts in Javascript? The only relatively-new part is destructuring assignment, but that's been around since 2015, since it was added in ES6.
I’ve found returning a tuple with my validation functions to be very helpful.<p><pre><code> let [isValid, err] = validate(data)
</code></pre>
It’s nice for a few reasons:<p>1. I know anything returned `err` is safe to display back to the user<p>2. Using the array (as opposed to an object) can allow me to name the values when I destructure so it can be used multiple times in the same block with useful naming.<p>3. I can destructure just the first half `[isValid]` if that’s all I care about.<p>4. More generally it helps keep the code readable. Other control flows might rely on some casting, assumptions, or exceptions but this way presents a nice customizable api for users writing the code, and a readable api for those reviewing the code.
While there are isolated use cases for returning multiple values (quotient/remainder being a good example), all of the real-world cases I've seen where the author tried have been a serious code smell, a missed warning that the encapsulation was weak. Refactoring to use single return values or coherent value objects almost always produced cleaner, more readable, more testable code as a result.
I don't understand what kind of stuff people build in React where performance implications of this sort is relevant. I'm building games where I loop through potentially thousands of objects 60 times a second and optimizations on that level still don't make any difference. It's always rendering that is the bottleneck. Shouldn't it be the same with React?
This is one of the main reasons I love using Go for backend work, and the lack of this functionality is just one of the reasons I dislike JavaScript.<p>Anything to make JS feel less haphazard and more elegant (i.e. using TypeScript) is awesome in my books. Looking forward to hopefully using this pattern in my personal work going forward, and maybe trying to introduce it to my team ta work.
C# also supports this with the Tuple type<p><a href="https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/builtin-types/value-tuples#tuple-assignment-and-deconstruction" rel="nofollow">https://docs.microsoft.com/en-us/dotnet/csharp/language-refe...</a>
So instead of returning a object, we stuff two values into an array and this grants us the advantage of saving a few extra characters.<p>This is pretty hacky and it smells. it also won't work in languages like typescript (without losing the advantage of using it) which is frequently used.