News for hackers. Stuff that matters.
Re:Copying objects in JavaScript by fendrak on Tuesday November 13, 2018 @01:08PM (#18443170)
Indeed it can, but I believe the point is that it's not round-tripable, meaning you can't parse the resulting serialized JSON back into its original form, the one that contained the Date objects.

If you could do so, JSON.stringify/parse would be a convenient way to do a deep clone.

Re:Copying objects in JavaScript by simlevesque on Tuesday November 13, 2018 @01:12PM (#18443210)
Yeah that's right. All I'm saying is that no matter what, the following sentence is false:

> An example of a non-serializable value type is the Date object - it is printed in a non ISO-standard format and cannot be parsed back to its original value :(.

Re:Copying objects in JavaScript by zachrose on Tuesday November 13, 2018 @01:18PM (#18443286)
It would be cool if there was a webpage for β€œIs your function ______?” with a list of things that functions can be:

- Roundtrip-able (reversible?)

- Pure

- Effectful

- Mutation-doing

- Idempotent/Nullipotent

- Algebraically closed over the set of its inputs

- Et c.

Every time I hear about a new one I wish I had such a list

Re:Copying objects in JavaScript by phiresky on Tuesday November 13, 2018 @01:47PM (#18443591)
> - Roundtrip-able (reversible?)

You mean injective

Re:Copying objects in JavaScript by kccqzy on Tuesday November 13, 2018 @04:17PM (#18444988)
> Roundtrip-able (reversible?)

Involution, if you mean calling a function twice will give the original input.