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

do not release unfinished features

Browse source
This commit is contained in:
jackdotink 2024-12-01 14:07:05 -06:00
parent 03608c7519
commit 34aff1a162
No known key found for this signature in database
1 changed files with 23 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
docs/do-not-release-unfinished-features.md Normal file
View file

@ -0,0 +1,23 @@
# Do Not Release Unfinished Features
## Summary
Luau should not ship incomplete or unusable features that are not ready for users, even if part of the feature is ready.
## Motivation
Recently, Luau has released the vector primitive type and vector standard library. However, only the VM part of the vector was ready for release. The analysis vector primitive is, at the time of writing, completely unusable. Releasing unfinished and unusable features can lead to confusion and frustration among users and will ultimately turn people away from the language. It also harms tooling, like Luau-LSP, which struggles to support these features which are not ready for users.
## Design
This RFC adds no language features, and is instead a change to how Luau releases features. Under this RFC, Luau will not release features that are not ready in every sense of the word.
As most users get their FFlags from Roblox, and Luau is a Roblox product, for the purposes of this RFC, Roblox enabling a FFlag is the same as Luau releasing a feature.
## Drawbacks
This RFC has the drawback of slowing down the release of new features. However, this is necessary to ensure that what is released is ready for users.
## Alternatives
Instead of adopting this RFC, trust can be placed in the Luau team to not release features prematurely in the future.