-
Notifications
You must be signed in to change notification settings - Fork 107
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
Declare crate for generated proto Rust code #4701
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice cleanup
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
@@ -20,9 +20,6 @@ | |||
extern crate alloc; | |||
|
|||
use core::assert_matches::assert_matches; | |||
use std::sync::Arc; | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like this uses an older version of formatting. Since #4648 it rustfmt should automatically group use statements.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rustfmt is actively adding a space there. I think it's adding a space dividing external imports from workspace imports.
c7a16a4
to
473438b
Compare
I think we could drop the |
Attempt 2.
Use the same approach as we use in internal repo: build generated proto Rust code in its own package (crate).
#4565