From d95132ebfb6b562e096c82238ddbf917486ee22f Mon Sep 17 00:00:00 2001 From: Junseo Yoo Date: Wed, 31 Jul 2024 23:49:46 -0700 Subject: [PATCH] optional arguments does not mean you don't need to write it --- docs/user-defined-type-functions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-defined-type-functions.md b/docs/user-defined-type-functions.md index 02fc612..5d26958 100644 --- a/docs/user-defined-type-functions.md +++ b/docs/user-defined-type-functions.md @@ -72,7 +72,7 @@ Because the name clashes with the global function `type()`, the `type` userdata'
`type` library (dropdown) -Methods under a different heading (ex: Singleton) imply that the methods are only available for those types. All attributes of newly created `type` instances are initialized with empty tables / arrays and `nil`. Methods with optional arguments will by default set arguments to the leftmost attribute. For instance, `type.newtable(X, Y)` will set properties to be `X`, indexer to be `Y`, and metatable to be `nil`. Additionally, all arguments are passed by references. +Methods under a different heading (ex: Singleton) imply that the methods are only available for those types. All attributes of newly created `type` instances are initialized with empty tables / arrays and `nil`. All arguments are passed by references. #### `type`