From e609f9c08480a0f1c75d1675ade3bf6a89f89107 Mon Sep 17 00:00:00 2001
From: ffrostfall <80861876+ffrostfall@users.noreply.github.com>
Date: Wed, 6 Nov 2024 13:54:08 -0500
Subject: [PATCH] Add reference to metatable-type-syntax

---
 docs/metatable-type-functions.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/metatable-type-functions.md b/docs/metatable-type-functions.md
index f6a0b34..e09a659 100644
--- a/docs/metatable-type-functions.md
+++ b/docs/metatable-type-functions.md
@@ -74,4 +74,6 @@ The name of `setmetatable` has an interpretation of implying a side effect; tabl
 
 ## Alternatives
 
+Do nothing, and rely on unique metatable type syntax to achieve what a `setmetatable` type function would achieve. However, this still has the issue of `getmetatable`. It is flat out incorrect at the moment, and a type function would be an ideal solution to that problem. If a type function is introduced, then any user could reasonably expect a counterpart `setmetatable` type function. Both metatable type functions and metatable syntax can exist at the same time, and that might be ideal.
+
 Do nothing. `typeof` solves the current issues with accessibility to the current object-oriented programming patterns, and the issue relating to getmetatable can be solved by overloads.