Fix example in documentation

[rap2hpoutre]

see #359

I choose to write:

assert_eq!("2010".to_string(), caps["year"]);

But I could have choose:

assert_eq!("2010", &caps["year"]);

Not sure which one is the best (maybe none of them)

[BurntSushi]

I think I actually prefer the &caps["year"] approach better, since it's more likely to match up with what you'll need in actual code. That is, caps["year"] has type str, which usually doesn't work.

Also, could you include the string Fixes #359 in the commit message and make sure the PR is squashed to one commit?

Thanks for doing this!

[rap2hpoutre]

Thanks!! I changed the approach and added Fixes #359 in commit. For the squash, do you need me to do it? Or will you do it in merging? (I remember github has an option to "squash and merge", but I can (try to) do it myself)

[BurntSushi]

@rap2hpoutre We unfortunately don't use the Github UI to merge PRs. Instead, we have a bot do it (which checks that the merge passes CI before pushing to master, which Github doesn't do).

To squash, just do git rebase -i master in a checkout of your PR branch (but make sure your master branch is up to date before doing so). Then type squash next to your Fixes #359 commit. Save and quit your editor. And then touch up the commit message when git opens your editor again. Finally, git push origin patch-1 --force.

[rap2hpoutre]

Done! Thanks again!

[BurntSushi]

Poifect! Thanks! @bors r+

[bors]

📌 Commit b9ac569 has been approved by BurntSushi

[bors]

⌛ Testing commit b9ac569 with merge e9f8318...

[bors]

☀️ Test successful - status-appveyor, status-travis
Approved by: BurntSushi
Pushing e9f8318 to master...