Render with Display using autoref specialization

[simonask]

This may not be something you're interested in merging. No hard feelings if you close this outright. :-)

I found for my use case that I needed to write display(...) in a lot of places, especially in cases where I was using external types (especially the many datetime formatting types from icu).

This PR adds autoref-based specialization to the html! macro such that it will choose a type's Render implementation if it is available, and use Display as a fallback.

The blanket impl of Render for T where T: Display was removed in #271 for good reasons, and I will try to justify this PR in terms of those reasons:

• 266 (Impl Render for borrows): This PR does not add any new blanket impls of Render or Display.

• Performance: Due to specialization, integers can still be rendered using itoa.
• Semantics: Arguably, Display is intended to provide a human-readable string. While this isn't necessarily tied to the HTML representation of the thing, it is not unreasonable to want to use the output of Display in HTML. This solution treats the output of Display as unescaped content (so it will be escaped before appending, by going through maud::display(...)). If a situation arises where the Display and Render implementations should be completely different, specialization allows this on a per-type basis.

The main drawback of this PR is that compiler errors are slightly more confusing when a type implements neither Render nor Display. I have tried to name the magic inner types used in the macro with that in mind.

Let me know what you think. :-)

[lambda-fairy]

Thanks and sorry for the delay!

I didn't expect the solution to be so clean – seeing your take validates the approach for me.

Let's merge this for now and see what people think in the next release.