-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Announcing Rust 1.82.0 #1415
Announcing Rust 1.82.0 #1415
Commits on Oct 15, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 9d8b876 - Browse repository at this point
Copy the full SHA 9d8b876View commit details
Commits on Oct 16, 2024
-
Update the
min_exhaustive_patterns
sectionCo-authored-by: Kevin Reid <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for c4b85e3 - Browse repository at this point
Copy the full SHA c4b85e3View commit details -
Don't call "NaN boxing" an optimization
Co-authored-by: Kevin Reid <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for e6c5601 - Browse repository at this point
Copy the full SHA e6c5601View commit details -
Spell out
repr(packed)
structsCo-authored-by: Kevin Reid <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for a8658a5 - Browse repository at this point
Copy the full SHA a8658a5View commit details -
Link to
no_mangle
in the referenceCo-authored-by: Kevin Reid <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 3426f0e - Browse repository at this point
Copy the full SHA 3426f0eView commit details -
Configuration menu - View commit details
-
Copy full SHA for c51207a - Browse repository at this point
Copy the full SHA c51207aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 414e454 - Browse repository at this point
Copy the full SHA 414e454View commit details -
Use
&raw mut STATIC_MUT
in forward-looking codeCo-authored-by: Travis Cross <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 27e63bd - Browse repository at this point
Copy the full SHA 27e63bdView commit details
Commits on Oct 17, 2024
-
Co-authored-by: Travis Cross <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 6a1bf3c - Browse repository at this point
Copy the full SHA 6a1bf3cView commit details -
Co-authored-by: Travis Cross <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for d950248 - Browse repository at this point
Copy the full SHA d950248View commit details -
Configuration menu - View commit details
-
Copy full SHA for d735b97 - Browse repository at this point
Copy the full SHA d735b97View commit details -
Add a section for unsafe extern
Co-authored-by: Travis Cross <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for ead205c - Browse repository at this point
Copy the full SHA ead205cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 26498ab - Browse repository at this point
Copy the full SHA 26498abView commit details -
Configuration menu - View commit details
-
Copy full SHA for 0d73760 - Browse repository at this point
Copy the full SHA 0d73760View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2d61ada - Browse repository at this point
Copy the full SHA 2d61adaView commit details -
Co-authored-by: Ralf Jung <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 307525a - Browse repository at this point
Copy the full SHA 307525aView commit details -
Add section on precise capturing
use<..>
syntaxThanks to CE for details on the compiler's use-case that informs an example here.
Configuration menu - View commit details
-
Copy full SHA for 8970b99 - Browse repository at this point
Copy the full SHA 8970b99View commit details -
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.
Configuration menu - View commit details
-
Copy full SHA for 2b4aef0 - Browse repository at this point
Copy the full SHA 2b4aef0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 632ea50 - Browse repository at this point
Copy the full SHA 632ea50View commit details -
Configuration menu - View commit details
-
Copy full SHA for de10a88 - Browse repository at this point
Copy the full SHA de10a88View commit details -
Say "use" rather than "call" for
unsafe extern
itemsWe 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.
Configuration menu - View commit details
-
Copy full SHA for 28d1fb5 - Browse repository at this point
Copy the full SHA 28d1fb5View commit details -
Configuration menu - View commit details
-
Copy full SHA for a0e67b9 - Browse repository at this point
Copy the full SHA a0e67b9View commit details -
It's more correct to say "were" rather than "was" here, and it sounds better to my ear.
Configuration menu - View commit details
-
Copy full SHA for a89f927 - Browse repository at this point
Copy the full SHA a89f927View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4b6db4e - Browse repository at this point
Copy the full SHA 4b6db4eView commit details -
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.
Configuration menu - View commit details
-
Copy full SHA for d307a98 - Browse repository at this point
Copy the full SHA d307a98View commit details