From 0b998a2d438db141498645809549c65abb520dbb Mon Sep 17 00:00:00 2001 From: Qualadore Date: Tue, 11 Jul 2023 11:01:14 +0000 Subject: [PATCH] Clarify uniqueness --- rfcs/function-debug-id.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rfcs/function-debug-id.md b/rfcs/function-debug-id.md index 2b8e8799..95e7300f 100644 --- a/rfcs/function-debug-id.md +++ b/rfcs/function-debug-id.md @@ -2,7 +2,7 @@ ## Summary -Add `debug.id` which accepts a value and always returns the identifier unique to all values that haven't been garbage collected. +Add `debug.id` which accepts a value and always returns the identifier unique to that value. ## Motivation @@ -12,7 +12,7 @@ When debugging, it is often useful to compare identity. Usually `print` will pri ## Design -`debug.id(value: string | userdata | table | thread | function): number` always returns the identifier unique to that value, and is not possible to override. Uniqueness is only guaranteed for values that haven't been garbage collected. +`debug.id(value: string | userdata | table | thread | function): number` always returns the identifier unique to that value, and is not possible to override. The identifier can be reused after the value associated with it is garbage collected. While tables and userdata have individualized metatables, also allowing functions and threads to be passed to `debug.id` would let their type-level `__tostring` be redefined. Strings are useful to accept because of long, similar strings.