Documentation fix due to latest changes in the crate.

[JustForFun88]

Due to merged PR #357, #362 I think that we need to fix docummentation.

Fixed broken links in HashMap::raw_table and HashSet::raw_table, as well as some typos and mistakes elsewhere (especially in EntryRef::or_insert_with_key).

To fix #349, I removed capacity comparisons in all places (except drain and clear), however left the phrase "keeps the allocated memory for reuse", because although the erase method may not release the capacity, the subsequent rehash_in_place function definitely will release all.

Close #349.

[JustForFun88]

Rust / test (ubuntu-latest, i586-unknown-linux-gnu, nightly) tests fail because of: error: linking with cc failed: exit status: 1??

[JustForFun88]

Issue rust-lang/rust#102703

[Amanieu]

Thanks! This is a great improvement to the documentation.

[Amanieu]

@bors r+

[bors]

📌 Commit dfe2496 has been approved by Amanieu

It is now in the queue for this repository.

[bors]

🔒 Merge conflict

This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again.

How do I rebase?

Assuming self is your fork and upstream is this repository, you can resolve the conflict following these steps:

1. git checkout fix_doc (switch to your branch)
2. git fetch upstream master (retrieve the latest master)
3. git rebase upstream/master -p (rebase on top of it)
4. Follow the on-screen instruction to resolve conflicts (check git status if you got lost).
5. git push self fix_doc --force-with-lease (update this PR)

You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial.

Please avoid the "Resolve conflicts" button on GitHub. It uses git merge instead of git rebase which makes the PR commit history more difficult to read.

Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Cargo.lock conflict is handled during merge and rebase. This is normal, and you should still perform step 5 to update this PR.

Error message

Auto-merging src/set.rs
Auto-merging src/map.rs
CONFLICT (content): Merge conflict in src/map.rs
Automatic merge failed; fix conflicts and then commit the result.

[bors]

☔ The latest upstream changes (presumably #355) made this pull request unmergeable. Please resolve the merge conflicts.

[Amanieu]

@bors r+

[bors]

📌 Commit 47bc623 has been approved by Amanieu

It is now in the queue for this repository.

[bors]

⌛ Testing commit 47bc623 with merge 101b8de...

[bors]

☀️ Test successful - checks-actions
Approved by: Amanieu
Pushing 101b8de to master...