From 7938996ef6805e14216d1b3c0eb19e830348d4fb Mon Sep 17 00:00:00 2001 From: karl-police Date: Wed, 31 Jul 2024 19:24:07 +0200 Subject: [PATCH] Update user_defineable_self_namecall_type.md --- docs/user_defineable_self_namecall_type.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user_defineable_self_namecall_type.md b/docs/user_defineable_self_namecall_type.md index 26c2e5a..753f55f 100644 --- a/docs/user_defineable_self_namecall_type.md +++ b/docs/user_defineable_self_namecall_type.md @@ -137,7 +137,7 @@ But this is a **metatable** in a class-construction context. Even Lua designs th -### Strict Type Alternative +### Fixed type defined Alternative This is an alternative that I captured off from **react-lua**. ```lua @@ -166,4 +166,4 @@ function Class:TestMethod() end ``` -``self`` is now a ``string``. By defining ``[string]`` the automatic type resolver won't automatically put the actual things defined in the code into that table as well. That's why it isn't that good, but it's very smart. +``self`` is now a ``string``. By defining ``[string]`` the automatic type resolver won't automatically put the actual things defined in the code into that table as well. That's why it isn't that good, but it's very smart. Hence why I called it "fixed" as in, _the definition is strictly already given._