-
Notifications
You must be signed in to change notification settings - Fork 889
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
skip_macro_invocations: Cannot configure from rustfmt.toml
#5816
Comments
It also seems that there is some difference in behaviour between |
3 tasks
DCNick3
added a commit
to DCNick3/iroha
that referenced
this issue
Jul 5, 2023
…ks, I hate it) `rustfmt` wants `socket_addr!(127.0.0.1: port);` to be formatted as `socket_addr!(127.0.0 .1: port);`... There is an option to exclude a certain macro invocations from being formatted, but 1) the config option parsing seems broken rust-lang/rustfmt#5816 2) the toolchain used in CI doesn't support it I guess we would have to live with this ugly formatting for some time... Signed-off-by: Nikita Strygin <DCNick3@users.noreply.github.com>
Thanks for a swift fix! |
DCNick3
added a commit
to DCNick3/iroha
that referenced
this issue
Jul 6, 2023
…ks, I hate it) `rustfmt` wants `socket_addr!(127.0.0.1: port);` to be formatted as `socket_addr!(127.0.0 .1: port);`... There is an option to exclude a certain macro invocations from being formatted, but 1) the config option parsing seems broken rust-lang/rustfmt#5816 2) the toolchain used in CI doesn't support it I guess we would have to live with this ugly formatting for some time... Signed-off-by: Nikita Strygin <DCNick3@users.noreply.github.com>
DCNick3
added a commit
to hyperledger-iroha/iroha
that referenced
this issue
Jul 6, 2023
`rustfmt` wants `socket_addr!(127.0.0.1: port);` to be formatted as `socket_addr!(127.0.0 .1: port);`... There is an option to exclude a certain macro invocations from being formatted, but 1) the config option parsing seems broken rust-lang/rustfmt#5816 2) the toolchain used in CI doesn't support it I guess we would have to live with this ugly formatting for some time... Signed-off-by: Nikita Strygin <DCNick3@users.noreply.github.com>
mversic
pushed a commit
to hyperledger-iroha/iroha
that referenced
this issue
Oct 17, 2023
`rustfmt` wants `socket_addr!(127.0.0.1: port);` to be formatted as `socket_addr!(127.0.0 .1: port);`... There is an option to exclude a certain macro invocations from being formatted, but 1) the config option parsing seems broken rust-lang/rustfmt#5816 2) the toolchain used in CI doesn't support it I guess we would have to live with this ugly formatting for some time... Signed-off-by: Nikita Strygin <DCNick3@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
skip_macro_invocations
option doesn't parse as documented.Writing
skip_macro_invocations=["*", "println"]
inrustfmt.toml
leads to this error:It seems that parsing rules are not what is actually designed (
*
or some name), but more like tagged serde enum. These config files work:The text was updated successfully, but these errors were encountered: