The heart example in docs for std::char primitive is ambiguous

[ljedrz]

I was going through the docs for std::char and found out that the heart is at first encoded with two codepoints (❤️) and just one afterwards (❤). This is misleading, as the difference is not visible in the browser (at least not in Chrome) and the reader first sees information that:

Trying to create a literal with let heart = '❤️'; gives an error

and afterwards there are perfectly valid examples like

for c in '❤'.escape_unicode() {
    print!("{}", c);
}

What makes matters worse is that they both start with the same code point; the second example I listed states that:

This prints:
\u{2764}

While in the first case there is:

assert_eq!(Some('\u{2764}'), iter.next());
assert_eq!(Some('\u{fe0f}'), iter.next());

I found this misleading and had to use a hex editor to discover the difference.

[steveklabnik]

Interesting, your browsers render these the same? They're very different here:

[ljedrz]

Yes, and the same on my phone (Bugsplorer or Edge as they now call it). I will provide the desktop screenshot when I have the chance; I can attach a screenshot from my phone for now:

[ljedrz]

Screenshot from a PC using the current stable Chrome:

I think there is a little difference in size, but it's not apparent, since in the docs they are far apart.

At my work I also use Chrome with a different font and both hearts are plain black.

[ljedrz]

This is how the two-codepoint and one-codepoint examples look like in another Chrome; when formatted as code, they look the same:

[frewsxcv]

This will be fixed by #43919.