You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you place an unstable config in a rustfmt.toml config file and run
using a stable version of rustfmt the config is ignored and you get the
following:
$ cargo fmt
Warning: can't set `merge_imports = true`, unstable features are only available in nightly channel.
But if you instead pass the config using the '--config' option rustfmt
happily applies and uses the unstable config:
$ cargo fmt -- --config merge_imports=true
I don't know if this is intentional or not but it gave me a workaround for using the 'merge_imports' feature while using a stable toolchain: diem/diem#2926
The text was updated successfully, but these errors were encountered:
Yeah I noticed this the other day too (#4064 (comment)). I don't think it's intentional currently, and it's possible that cli config override support for unstable options on stable will be dropped as part of the rustfmt 2.x release
If you place an unstable config in a rustfmt.toml config file and run
using a stable version of rustfmt the config is ignored and you get the
following:
But if you instead pass the config using the '--config' option rustfmt
happily applies and uses the unstable config:
I don't know if this is intentional or not but it gave me a workaround for using the 'merge_imports' feature while using a stable toolchain: diem/diem#2926
The text was updated successfully, but these errors were encountered: