New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Being clear about not (yet) standard feature #100
Comments
Hi @QuentinRoy , This document is about language features used in a big number of codebases existing and to come, so if a language feature is explained there it's because people already use it. But you are right to point out that some feature are not fully standardized yet and it could be written when its the case. Anyway, if such a feature (like object rest) would have a different behavior when standardized, there would be a nice and clear transition path considering the number of people already using it. If it were the case, I would say how to do it immediately via a PR. If you are willing to add an indication for non-standardized features in the document, feel free to submit a PR 👍 . |
I find it dangerous to encourage people to use not yet standardized features of the language.
For example, object rest/spread is still in stage 3, but that is not mentioned in the guide.
The text was updated successfully, but these errors were encountered: