luau-lang/rfcs
1
0
Fork 0
mirror of https://github.com/luau-lang/rfcs.git synced 2025-05-04 10:43:48 +01:00
Code Issues Projects Releases Packages Wiki Activity

Minor adjustments.

Browse source
This commit is contained in:
Andy Friesen 2024-01-12 15:47:35 -08:00
parent 0b9b917ea1
commit 66e1e2a434
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
docs/syntax-property-access-modifiers.md
View file

@ -2,7 +2,7 @@
## Summary ## Summary
We need syntax to match the semantics of read-only and writed-only modifiers for table properties and indexers. We need syntax to match the semantics of read-only and write-only modifiers for table properties and indexers.
## Motivation ## Motivation
@ -76,10 +76,10 @@ and is pretty easy to parse efficiently.
## Drawbacks ## Drawbacks
We expect it to be very commonplace to have table types containing read-only We expect it to be very commonplace to have table types containing read-only
functions. This syntax is a little bit verbose and maybe not intuitive for that functions. This syntax is a little bit verbose and maybe unintuitive for that
use case. use case.
`read` and `write` are also really useful method names. It's a little bit `read` and `write` are also very useful method names. It's a little bit
awkward to talk about a table that has a `read` or a `write` method: awkward to talk about a table that has a `read` or a `write` method:
```lua ```lua
@ -164,7 +164,7 @@ example
type Foo = { p: number?+ } type Foo = { p: number?+ }
``` ```
### How to parse or serialize properties with differing read- and write-types? ### How do we talk about properties with differing read- and write-types?
One corner case is that type inference may deduce different read- and One corner case is that type inference may deduce different read- and
write-types, which need to be presented to the user. For example the write-types, which need to be presented to the user. For example the