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
Thanks for sharing this observation but binop_separator is by design only applicable to binary expressions, and does not apply to compound constraints regardless of the fact that the latter utilizes one of the same symbols.
[…] If you'd like to have a new config option that could be used to control that behavior in bounds then please open a new issue and we'll take that through the standard process to consider new options.
…which makes sense. However, it leaves rustfmt without a way to configure how constraints are formatted, whereas there are similar options for other contexts (i.e. binop_separator). I personally think this should be configurable, as setting binop_separator to "Back" in a project leaves +-signs at the front in only this case.
I would propose that this new option have the same "Front" and "Back" values available in order to maintain a consistent style across projects.
Thanks for your consideration!
The text was updated successfully, but these errors were encountered:
Coming from #4941. In that issue I suggested that
binop_separator
be used to control situations such as the following:On the above, @calebcartwright said:
…which makes sense. However, it leaves
rustfmt
without a way to configure how constraints are formatted, whereas there are similar options for other contexts (i.e.binop_separator
). I personally think this should be configurable, as settingbinop_separator
to "Back" in a project leaves+
-signs at the front in only this case.I would propose that this new option have the same "Front" and "Back" values available in order to maintain a consistent style across projects.
Thanks for your consideration!
The text was updated successfully, but these errors were encountered: