It will have issues with anything non-serializable, explicitly set undefineds will disappear on objects (if that matters), and undefined inside arrays will turn into null. And maybe some other edge cases I'm forgetting.
It will implode on undefined, circular references, and most appallingly, objects with different key orders. Not really obscure edge cases. People really need to stop using the JSON trick.
You don't need to create an arrow function each time you want to call only one function. This works:
[ ... new Set(arr.map(JSON.stringify))].map(JSON.parse)
You would need though if the function depended on the context (the JSON object in this case isn't needed for the function itself), or you could .bind it too
13
u/[deleted] Mar 19 '19
[...new Set(arr.map(x => JSON.stringify(x))].map(x => JSON.parse(x))
Same thing, but with arrays of objects. Apparently probably deterministic but maybe not it depends ohgodhelpme