about summary refs log tree commit diff
path: root/docs/dev/debugging.md
diff options
context:
space:
mode:
authorbors[bot] <26634292+bors[bot]@users.noreply.github.com>2021-05-10 20:10:59 +0000
committerGitHub <noreply@github.com>2021-05-10 20:10:59 +0000
commit77f0c92fd8311bccc001ddaf9eb72662d35e9836 (patch)
treebdc532c6318c3378de63649ae65a4f420aa7db2a /docs/dev/debugging.md
parentc7edc38cd0c55ea85356112608bbb928856f6865 (diff)
parent59c2efe4b6de41424a5bfd2a0cb59a43ffc11042 (diff)
downloadrust-77f0c92fd8311bccc001ddaf9eb72662d35e9836.tar.gz
rust-77f0c92fd8311bccc001ddaf9eb72662d35e9836.zip
Merge #8794
8794: Give MergeBehaviour variants better names r=Veykril a=Veykril

I never really liked the variant names I gave this enum from the beginning and then I found out about rustfmt's `imports_granularity` config:

> imports_granularity
>
> How imports should be grouped into use statements. Imports will be merged or split to the configured level of granularity.
> 
>     Default value: Preserve
>     Possible values: Preserve, Crate, Module, Item
>     Stable: No

I personally prefer using `crate` over `full` and `module` over last, they seem more descriptive. Keeping these similar between tooling also seems like a good plus point to me.

We might even wanna take over the entire enum at some point if we have a `format/cleanup imports` assists in the future which would probably want to also have the `preserve` and `item` options.

Co-authored-by: Lukas Wirth <lukastw97@gmail.com>
Diffstat (limited to 'docs/dev/debugging.md')
0 files changed, 0 insertions, 0 deletions