From f45b08be4aa3ae06113721d147802b3691cb4512 Mon Sep 17 00:00:00 2001 From: aaron Date: Tue, 27 Aug 2024 19:16:09 -0700 Subject: [PATCH] Update docs/user-defined-type-functions.md Co-authored-by: vegorov-rbx <75688451+vegorov-rbx@users.noreply.github.com> --- 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 788fd24..ffc42d4 100644 --- a/docs/user-defined-type-functions.md +++ b/docs/user-defined-type-functions.md @@ -92,7 +92,7 @@ Instead, this RFC proposes that we accept that type functions, like the rest of ### `types` API Reference -This section details the initial programming interface we propose for `type`s when they are reflected into type function bodies. Each section is separated by headers (e.g. Singleton) and describe the methods available to that category of type. The initial section, titled `types`, describes the elements of the interface common to every category of type. All attributes of newly-created `type`s are initialized with empty tables / arrays and `nil`. All arguments are passed by references. +This section details the initial programming interface we propose for `type`s when they are reflected into type function bodies. Each section is separated by headers (e.g. Singleton) and describe the methods available to that category of type. The initial section, titled `types`, describes the elements of the interface common to every category of type. All properties of newly-created `type`s are initialized with empty tables / arrays and `nil`. All arguments are passed by references.
Expand for full type API reference.