RFC: Style code/reset rendering via Display

[joshtriplett]

This is an unusual suggestion, but I've tried it out in practice and it feels really comfortable to use. I wanted to run it by you to see if it seemed reasonable.

I found the requirement to call .render() and .render_reset() rather verbose, particularly when trying to render several color styles in one line. I started thinking about ways to make that more convenient, and this idea occurred to me.

With this PR applied, Style and Reset implement Display directly, rendering the ANSI code, without having to call .render(). That part I'm hoping will be relatively uncontroversial; that's in the first two commits.

The more unusual part of this PR: if you set the alternate format flag, a Style will print its reset code, instead.

The combination of the two makes it easy to use inline formats to render styles. Here's an example of how this looks:

use anstyle::{AnsiColor, Style};

fn main() {
    const RB: Style = AnsiColor::Red.on_default().bold();
    const GU: Style = AnsiColor::Green.on_default().underline();
    println!("{RB}Hello{RB:#}, {GU}world{GU:#}!");
}

I'm hoping this seems reasonable. If you find the use of the alternate flag too much, though, then as an alternative, you could drop the last two commits, and that would still let people render codes and resets using inline styles:

use anstyle::{AnsiColor, Reset, Style};

fn main() {
    const RESET: Reset = Reset;
    const RB: Style = AnsiColor::Red.on_default().bold();
    const GU: Style = AnsiColor::Green.on_default().underline();
    println!("{RB}Hello{RESET}, {GU}world{RESET}!");
}

(This would get even easier if anstyle had a pub const RESET: Reset = Reset;, which I'd be happy to send in a patch for.)

[epage]

Moving the conversation over at #166.

• This is multiple decisions to be made and could have multiple PRs through the life of it
• I, and I assume users, are more likely to look up a discussion like this in the Issues, rather than PRs

[joshtriplett]

Thanks for the merge! I'm using the new API now, and it works well.