From 2723717f6e50f885155d09d6060d9c93404cf310 Mon Sep 17 00:00:00 2001 From: ccuser44 <68124053+ccuser44@users.noreply.github.com> Date: Sat, 14 Dec 2024 21:02:22 +0200 Subject: [PATCH] Remove useless comment --- docs/table.clone-locked-metatables.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/table.clone-locked-metatables.md b/docs/table.clone-locked-metatables.md index 9091e4c..8aeecca 100644 --- a/docs/table.clone-locked-metatables.md +++ b/docs/table.clone-locked-metatables.md @@ -65,7 +65,6 @@ However, this is not an issue as the changes proposed in this RFC do not allow f Another potential drawback that could be levied at this proposal is a reduced debuggability of not hard-failing when the expected behavior would be to create a shallow copy with the metatable of the original table. However, this point is most certainly moot in practice, as most users very likely are not even aware, or desire the fact that `table.clone` can assign the metatables of the original table to the clone. - ## Alternatives