From e2584682847d3ab242a0f2133fb07d48ef75e0bd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?C=C3=A9dric=20St-Jean?= Date: Sun, 22 Mar 2020 15:58:50 -0400 Subject: [PATCH] Remove outdated paragraph from deepcopy docstring (#35192) --- base/deepcopy.jl | 4 ---- 1 file changed, 4 deletions(-) diff --git a/base/deepcopy.jl b/base/deepcopy.jl index df12ccdf371f1e..0100affadbe300 100644 --- a/base/deepcopy.jl +++ b/base/deepcopy.jl @@ -13,10 +13,6 @@ independent object. For example, deep-copying an array produces a new array whos are deep copies of the original elements. Calling `deepcopy` on an object should generally have the same effect as serializing and then deserializing it. -As a special case, functions can only be actually deep-copied if they are anonymous, -otherwise they are just copied. The difference is only relevant in the case of closures, -i.e. functions which may contain hidden internal references. - While it isn't normally necessary, user-defined types can override the default `deepcopy` behavior by defining a specialized version of the function `deepcopy_internal(x::T, dict::IdDict)` (which shouldn't otherwise be used),