luau-lang/rfcs
1
0
Fork 0
mirror of https://github.com/luau-lang/rfcs.git synced 2025-04-20 11:53:49 +01:00
Code Issues Projects Releases Packages Wiki Activity

fix typos in method names

Browse source
This commit is contained in:
Junseo Yoo 2024-06-27 15:27:20 -07:00
parent 2906909bb2
commit e58213f629
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/user-defined-type-functions.md
View file

@ -30,7 +30,7 @@ type function rawget(tbl, prop)
error("First parameter of rawget is not a table!") -- fails to reduce error("First parameter of rawget is not a table!") -- fails to reduce
end end
return tbl.getProps()[prop.getValue()] return tbl.getprops()[prop.getvalue()]
end end
type Person = { type Person = {
@ -56,7 +56,7 @@ To give warnings, developers can use `print()` with custom warning messages. To
To allow Luau developers to modify the runtime values of types in type functions, this RFC proposes introducing a new userdata called `typelib`. An `typelib` object is a runtime representation of all types within the program and provides a basic set of library methods that can be used to modify types. As such, under the hood, each argument of a type function is serialized into a userdata called `typelib`. Most importantly, they are *only accessible within type functions* and are *not a runtime type for other use cases than type functions*. To allow Luau developers to modify the runtime values of types in type functions, this RFC proposes introducing a new userdata called `typelib`. An `typelib` object is a runtime representation of all types within the program and provides a basic set of library methods that can be used to modify types. As such, under the hood, each argument of a type function is serialized into a userdata called `typelib`. Most importantly, they are *only accessible within type functions* and are *not a runtime type for other use cases than type functions*.
<details><summary>typelib library methods (dropdown)</summary> <details><summary>typelib library methods (dropdown)</summary>
Note: methods under a different type heading (ex: `Singleton`) imply that the methods are only available for those types. At the implementation level, there is a check to make sure that the type-specific methods are being called on the correct types (e.g, for `getIndexer()`, assert that `isTable()` is true). Note: methods under a different type heading (ex: `Singleton`) imply that the methods are only available for those types. At the implementation level, there is a check to make sure that the type-specific methods are being called on the correct types (e.g, for `getindexer()`, assert that `istable()` is true).
#### Any #### Any
@ -131,7 +131,7 @@ The build / analysis times will also be negatively impacted by this feature as r
Currently, the runtime representation of types is a userdata called `typelib`. Another representation is to use the already-existing type in Luau `table`; instead of serializing types into `typelib`, we can serialize them into tables with predefined properties. For instance, the representation for a string singleton `"abc"` could be `{type = "stringSingleton", value = "abc"}`. So instead of writing: Currently, the runtime representation of types is a userdata called `typelib`. Another representation is to use the already-existing type in Luau `table`; instead of serializing types into `typelib`, we can serialize them into tables with predefined properties. For instance, the representation for a string singleton `"abc"` could be `{type = "stringSingleton", value = "abc"}`. So instead of writing:
```luau ```luau
type function isSingleton(t) type function isSingleton(t)
if t:isStringSingleton() then if t:isstringsingleton() then
return t return t
end end
end end