Deep Cloning Objects in JavaScript, the Modern Way

Re:Deep Cloning Objects in JavaScript, the Modern Way by Drakim on Friday December 22, 2023 @07:45AM (#38733590)

if "current" is a deep object here and contains other objects/arrays, you risk that wherever you are sending this shallow copy will mutate those deeper values and potentially mess things up for the code where "current" came from.

Maybe it's not a situation that comes up often, but it would be fairly hard to debug and guarding yourself against mysterious problems in advance is always neat.

[ Parent | on HN ]

Re:Deep Cloning Objects in JavaScript, the Modern Way by lambda_garden on Friday December 22, 2023 @07:49AM (#38733614)

In practice, I think it's easier to use linting and type-systems to prevent other code from mutating you stuff than defensive copying.

[ Parent | on HN ]

Re:Deep Cloning Objects in JavaScript, the Modern Way by VPenkov on Friday December 22, 2023 @08:38AM (#38734004)

You could make the same argument backwards though - many people may find it easier to do deep copies rather than throwing extra software they might not necessarily be familiar with.

[ Parent | on HN ]