From bfeb69988a211fb7b7108d63e7da6b698356b9af Mon Sep 17 00:00:00 2001 From: Arseny Kapoulkine Date: Mon, 14 Feb 2022 10:23:23 -0800 Subject: [PATCH] Update function-table-clone.md --- rfcs/function-table-clone.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/rfcs/function-table-clone.md b/rfcs/function-table-clone.md index d2bcabd6..799ab93e 100644 --- a/rfcs/function-table-clone.md +++ b/rfcs/function-table-clone.md @@ -48,8 +48,9 @@ conservative route. We are likely to relax this restriction in the future. ## Drawbacks -Adding a new function to `table` library theoretically increases complexity. In practice though, we already effectively implement `table.clone` internally for some VM optimizations, -so exposing this to the users bears no cost. +Adding a new function to `table` library theoretically increases complexity. In practice though, we already effectively implement `table.clone` internally for some VM optimizations, so exposing this to the users bears no cost. + +Assigning a type to this function is a little difficult if we want to enforce the "argument must be a table" constraint. It's likely that we'll need to type this as `table.clone(T): T` for the time being, which is less precise. ## Alternatives