Add RFC status fields (#39)

It seems more consistent and unambiguous if we mark RFCs as being
implemented when the implementation lands instead of expecting to
cross-reference documentation. That also makes it easier for us to flag
stale RFCs.
This commit is contained in:
Arseny Kapoulkine 2021-05-17 18:19:49 -07:00 committed by GitHub
parent 8956c7448e
commit d40107dc60
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
13 changed files with 25 additions and 1 deletions

View File

@ -52,4 +52,4 @@ When an RFC gets merged, the feature *can* be implemented; however, there's no s
To avoid having permanently stale RFCs, in rare cases Luau team can *remove* a previously merged RFC when the landscape is believed to change enough for a feature like this to warrant further discussion. To avoid having permanently stale RFCs, in rare cases Luau team can *remove* a previously merged RFC when the landscape is believed to change enough for a feature like this to warrant further discussion.
To track progress of implemented features, it's advised to follow documentation instead; while RFCs aren't meant to be user-facing documentation, recaps in particular can reference RFCs for additional context behind the changes. When an RFC is implemented and the implementation is enabled via feature flags, RFC should be updated to include "**Status**: Implemented" at the top level (before *Summary* section).

View File

@ -2,6 +2,8 @@
> Note: this RFC was adapted from an internal proposal that predates RFC process > Note: this RFC was adapted from an internal proposal that predates RFC process
**Status**: Implemented
## Summary ## Summary
`__eq` metamethod will always be called during `==`/`~=` comparison, even for objects that are rawequal. `__eq` metamethod will always be called during `==`/`~=` comparison, even for objects that are rawequal.

View File

@ -2,6 +2,8 @@
> Note: this RFC was adapted from an internal proposal that predates RFC process > Note: this RFC was adapted from an internal proposal that predates RFC process
**Status**: Implemented
## Summary ## Summary
Change \_VERSION global to "Luau" to differentiate Luau from Lua Change \_VERSION global to "Luau" to differentiate Luau from Lua

View File

@ -2,6 +2,8 @@
> Note: this RFC was adapted from an internal proposal that predates RFC process > Note: this RFC was adapted from an internal proposal that predates RFC process
**Status**: Implemented
## Summary ## Summary
Add `debug.info` as programmatic debug info access API, similarly to Lua's `debug.getinfo` Add `debug.info` as programmatic debug info access API, similarly to Lua's `debug.getinfo`

View File

@ -2,6 +2,8 @@
> Note: this RFC was adapted from an internal proposal that predates RFC process > Note: this RFC was adapted from an internal proposal that predates RFC process
**Status**: Implemented
## Summary ## Summary
Add string pack/unpack from Lua 5.3 for binary interop, with small tweaks to format specification to make format strings portable. Add string pack/unpack from Lua 5.3 for binary interop, with small tweaks to format specification to make format strings portable.

View File

@ -2,6 +2,8 @@
> Note: this RFC was adapted from an internal proposal that predates RFC process and as such doesn't follow the template precisely > Note: this RFC was adapted from an internal proposal that predates RFC process and as such doesn't follow the template precisely
**Status**: Implemented
## Summary ## Summary
Add `table.clear` function that removes all elements from the table but keeps internal capacity allocated. Add `table.clear` function that removes all elements from the table but keeps internal capacity allocated.

View File

@ -2,6 +2,8 @@
> Note: this RFC was adapted from an internal proposal that predates RFC process and as such doesn't follow the template precisely > Note: this RFC was adapted from an internal proposal that predates RFC process and as such doesn't follow the template precisely
**Status**: Implemented
## Design ## Design
This proposal suggests adding two new builtin table functions: This proposal suggests adding two new builtin table functions:

View File

@ -2,6 +2,8 @@
> Note: this RFC was adapted from an internal proposal that predates RFC process > Note: this RFC was adapted from an internal proposal that predates RFC process
**Status**: Implemented
## Summary ## Summary
Add special syntax for array-like table types, `{ T }` Add special syntax for array-like table types, `{ T }`

View File

@ -2,6 +2,8 @@
> Note: this RFC was adapted from an internal proposal that predates RFC process and as such doesn't follow the template precisely > Note: this RFC was adapted from an internal proposal that predates RFC process and as such doesn't follow the template precisely
**Status**: Implemented
## Design ## Design
A feature present in many many programming languages is assignment operators that perform operations on the left hand side, for example A feature present in many many programming languages is assignment operators that perform operations on the left hand side, for example

View File

@ -2,6 +2,8 @@
> Note: this RFC was adapted from an internal proposal that predates RFC process > Note: this RFC was adapted from an internal proposal that predates RFC process
**Status**: Implemented
## Summary ## Summary
Add `continue` statement to `for`, `while` and `repeat` loops using a context-sensitive keyword to preserve compatibility. Add `continue` statement to `for`, `while` and `repeat` loops using a context-sensitive keyword to preserve compatibility.

View File

@ -2,6 +2,8 @@
> Note: this RFC was adapted from an internal proposal that predates RFC process and as such doesn't follow the template precisely > Note: this RFC was adapted from an internal proposal that predates RFC process and as such doesn't follow the template precisely
**Status**: Implemented
## Design ## Design
This proposal suggests extending Lua number syntax with: This proposal suggests extending Lua number syntax with:

View File

@ -2,6 +2,8 @@
> Note: this RFC was adapted from an internal proposal that predates RFC process > Note: this RFC was adapted from an internal proposal that predates RFC process
**Status**: Implemented
## Summary ## Summary
Implement syntax for type ascriptions using `::` Implement syntax for type ascriptions using `::`

View File

@ -2,6 +2,8 @@
> Note: this RFC was adapted from an internal proposal that predates RFC process > Note: this RFC was adapted from an internal proposal that predates RFC process
**Status**: Implemented
## Summary ## Summary
Add syntax for ascribing a type to variadic pack (`...`). Add syntax for ascribing a type to variadic pack (`...`).