Announcing Rust 1.82.0 (#1415)

* Announcing Rust 1.82.0

* Update the `min_exhaustive_patterns` section

Co-authored-by: Kevin Reid <[email protected]>

* Don't call "NaN boxing" an optimization

Co-authored-by: Kevin Reid <[email protected]>

* Spell out `repr(packed)` structs

Co-authored-by: Kevin Reid <[email protected]>

* Link to `no_mangle` in the reference

Co-authored-by: Kevin Reid <[email protected]>

* Remove `Waker::waker`

* Avoid ARM64/AArch64 by calling it 64-bit ARM

* Use `&raw mut STATIC_MUT` in forward-looking code

Co-authored-by: Travis Cross <[email protected]>

* Lowercase "not a number"

Co-authored-by: Travis Cross <[email protected]>

* Update unsafe attributes

Co-authored-by: Travis Cross <[email protected]>

* Tweak wording of `cargo info` versions, and drop feature callout

* Add a section for unsafe extern

Co-authored-by: Travis Cross <[email protected]>

* Re-title unsafe extern

* Reorder lang sections

* Add code tags to `cargo info` output

* Clarify NaN behavior wrt `==`

Co-authored-by: Ralf Jung <[email protected]>

* Add section on precise capturing `use<..>` syntax

Thanks to CE for details on the compiler's use-case that informs an
example here.

* Tweak wording in header about `unsafe extern`

Since we're adding `unsafe extern` in this release, saying "safe items
with unsafe extern" rather than "safe items in unsafe extern" here
sounds more right to my ear.

* Remove stray word

* Remove a redundant "still"

* Say "use" rather than "call" for `unsafe extern` items

We can have static items as well as function items within an `extern`
block, so let's say "use" rather than "call" when referring to these.
Let's also give an example of a static item to show how `safe` allows
for safe access to these items.

* Lowercase "undefined behavior"

* Use subjunctive mood

It's more correct to say "were" rather than "was" here, and it sounds
better to my ear.

* Put backticks around `impl Trait`

* Improve some copy in the floats section

There were some long and grammatically involved sentences that it
makes sense to refactor a bit here for better readability.

---------

Co-authored-by: Kevin Reid <[email protected]>
Co-authored-by: Travis Cross <[email protected]>
Co-authored-by: Ralf Jung <[email protected]>