Closed as not planned
Description
Is the dart-lang team willing to re-visit the idea of a dedicated copy
function that allows users to create a deep or shallow copy of objects if it can be proven that there are no side effects (no setters present, etc.)?
How about a dedicated copy constructor/operator similar to C++ for when such a copy cannot be done safely?
The last issue I could find was created/updated over 6/3 years ago: #3367
Dart 2.1.0 (build 2.1.0-dev.9.4 f9ebf21)