-
Notifications
You must be signed in to change notification settings - Fork 63
Dry-run functionality #146
Comments
I'm not sure I understand. What would |
Oh, and depending on your answer, this seems like an issue better suited for the cargo repository, as the |
It would print out a diff of what it _would_ change. with cargo check you
still have to wonder about which suggestions would get applied, and how
…On Mon, Sep 17, 2018, 5:22 PM Pascal Hertleif ***@***.***> wrote:
I'm not sure I understand. What would --dry-run do? Not change the files?
Isn't that basically the same as doing cargo check instead of cargo fix,
then?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#146 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABivSI-MvL3FDHxMG1b4KSWp_zJXzKEiks5ub4zqgaJpZM4WrsnG>
.
|
From the 1.29 blog post:
As far as I understand, not all warnings showed by |
Ah, I see, writing the diff is an interesting idea. In theory you can write it to a Do you want to open this issue on the cargo repo, @ozkriff? Otherwise I can do it (but you probably have some concrete idea and use cases you could describe, too). |
👍 Will do in a few minutes.
Actually, no, I was just asked about this in the comments to russian translation of 1.29 announcement. |
Done: rust-lang/cargo#6040 |
I think this library will also need support for doing all this without editing, no? |
@Manishearth nah, all file handling is done in the cargo subcommand |
Closing in favor of rust-lang/cargo#6040. |
Is something like
--dry-run
planned? Or rustfix will always require a VCS?The text was updated successfully, but these errors were encountered: