Reverse String: Confusing Hint for Bonus Tests

[nitwhiz]

One of the first things you learn about Rust strings is that they are a valid UTF-8 sequence.

The hint about grapheme clusters made me question reality. The tools to iterate characters are there since 1.0.0, even though the random forum posts you find when googling "rust grapheme clusters" suggest something else.

IMHO, having such a niche big brain flex right in the first exercises isn't helpful and steers you away from using a standard language feature. (That being being input.chars()) - Also, one of the tests outside of the grapheme feature is already using wide characters, so byte-by-byte reversing already fails without the bonus tests.

Ref:

rust/exercises/practice/reverse-string/.docs/instructions.append.md

Lines 5 to 15 in 3a169d8

	Test your function on this string: `uüu` and see what happens.
	Try to write a function that properly reverses this string.
	Hint: grapheme clusters
	To get the bonus test to run, remove the ignore flag (`#[ignore]`) from the last test, and execute the tests with:
	```bash
	cargo test --features grapheme
	```
	You will need to use external libraries (a `crate` in rust lingo) for the bonus task.

I suggest to just remove the "Hint: grapheme clusters" and the sentence about the need for a crate. Calling the feature grapheme is alright, as this is the right place for gimmicky names.

I understand that this might've felt like the right place to introduce external crates.

[github-actions]

Hello. Thanks for opening an issue on Exercism 🙂

At Exercism we use our Community Forum, not GitHub issues, as the primary place for discussion. That allows maintainers and contributors from across Exercism's ecosystem to discuss your problems/ideas/suggestions without them having to subscribe to hundreds of repositories.

This issue will be automatically closed. Please use this link to copy your GitHub Issue into a new topic on the forum, where we look forward to chatting with you!

If you're interested in learning more about this auto-responder, please read this blog post.