Rustfmt-ing liblog v2.

[goyox86]

Hi Rustaceans!

This is the second version of running rustfmt on liblog #28898. There are only rustfmt suggested changes. Because I think that some patterns here (that I fixed up in the prev PR need to be discussed in detail.

//cc @nrc

[rust-highfive]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nikomatsakis (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

[cristicbz]

This seems wrong, it should be indented relative to beginning of LogDirective (above and below too).

[nrc]

I'd like to see if https://github.com/nrc/rustfmt/pull/449 fixes the odd formatting in the tests. The only other thing is the comment which needs fixing up, otherwise looks good!

[goyox86]

@nrc, @alexcrichton I've run latest rustfmt and semmed to fix the issues. Also manually aligned comments.

[nikomatsakis]

I'm inclined to r+, but I'll wait on what @alexcrichton thinks.

[nikomatsakis]

r? @alexcrichton

[nrc]

LGTM

@goyox86 thanks for the changes!

[goyox86]

Sweet! @nrc The CI bot will merge it. Or do I have to merge?

[alexcrichton]

@bors: r+ 94946db

Ah no worries @goyox86, now that @bors has the r+ it'll come along eventually and auto-merge

[bors]

📌 Commit 94946db has been approved by alexcrichton