Better build progress report

[Yamakaky]

Show a finer report of what's happening while compiling. I still have to handle the errors, verbose mode, and for some reason the line is not clean before output.
See https://asciinema.org/a/9act16135ictn6zxwf97nmx9g for the output.
Closes #3448.

[rust-highfive]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @brson (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. Due to 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.

[Yamakaky]

Update: documented and verbose mode are supported. Still have the line cleaning problem.

[alexcrichton]

Thanks for the PR! I'd love to improve the output of Cargo by default as I think there's definitely a lot of improvements we can make. Unfortunately I don't think we can rely on the escape codes here working across platforms, though, notably Windows. I'd also prefer to keep a consistent experience across platforms where possible.

I've also prototyped this before with cargo-fancy and I wonder if some ideas could be incorporated here as well?

[bors]

☔ The latest upstream changes (presumably #3490) made this pull request unmergeable. Please resolve the merge conflicts.

[alexcrichton]

Closing due to inactivity, but feel free to resubmit with a rebase!

[euclio]

Any interest in reviving this with something using https://github.com/mitsuhiko/indicatif?

[Yamakaky]

Why not.