remove some unncessary and/or misleading methods of copy
#15675
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think it's better not to define
copyon objects where it doesn't make sense and doesn't do anything. IIRC, most of these definitions were introduced a long time ago when they might have been needed for copying ASTs. That was silly, and has been replaced by the internalastcopyfunction that knows how to copy only what's needed.These can cause problems, such as writing
copy(str).dataand thinking you'll get a new copy of the string's data.To minimize breakage, I'm leaving the definitions for
RangeandNumberfor now, since there is some code that assumes all array-like things are copyable.