mirror of
https://github.com/rust-lang/rust-analyzer
synced 2025-01-27 20:35:09 +00:00
Clarify feature policy
This commit is contained in:
parent
c6e1e17a10
commit
05514d8233
1 changed files with 2 additions and 0 deletions
|
@ -479,7 +479,9 @@ It is not cheap enough to enable in prod, and this is a bug which should be fixe
|
||||||
### Configurability
|
### Configurability
|
||||||
|
|
||||||
rust-analyzer strives to be as configurable as possible while offering reasonable defaults where no configuration exists yet.
|
rust-analyzer strives to be as configurable as possible while offering reasonable defaults where no configuration exists yet.
|
||||||
|
The rule of thumb is to enable most features by default unless they are buggy or degrade performance too much.
|
||||||
There will always be features that some people find more annoying than helpful, so giving the users the ability to tweak or disable these is a big part of offering a good user experience.
|
There will always be features that some people find more annoying than helpful, so giving the users the ability to tweak or disable these is a big part of offering a good user experience.
|
||||||
|
Enabling them by default is a matter of discoverability, as many users end up don't know about some features even though they are presented in the manual.
|
||||||
Mind the code--architecture gap: at the moment, we are using fewer feature flags than we really should.
|
Mind the code--architecture gap: at the moment, we are using fewer feature flags than we really should.
|
||||||
|
|
||||||
### Serialization
|
### Serialization
|
||||||
|
|
Loading…
Reference in a new issue