rust/library/std/src/lib.rs, branch 1.56.1

Auto merge of #87580 - ChrisDenton:win-arg-parse-2008, r=m-ou-se

2021-09-02T16:16:13+00:00

Update Windows Argument Parsing Fixes #44650 The Windows command line is passed to applications [as a single string](https://docs.microsoft.com/en-us/archive/blogs/larryosterman/the-windows-command-line-is-just-a-string) which the application then parses to get a list of arguments. The standard rules (as used by C/C++) for parsing the command line have slightly changed over the years, most recently in 2008 which added new escaping rules. This PR implements the new rules as [described on MSDN](https://docs.microsoft.com/en-us/cpp/cpp/main-function-command-line-args?view=msvc-160#parsing-c-command-line-arguments) and [further detailed here](https://daviddeley.com/autohotkey/parameters/parameters.htm#WIN). It has been tested against the behaviour of C++ by calling a C++ program that outputs its raw command line and the contents of `argv`. See [my repo](https://github.com/ChrisDenton/winarg/tree/std) if anyone wants to reproduce my work. For an overview of how this PR changes argument parsing behavior and why we feel it is warranted see https://github.com/rust-lang/rust/pull/87580#issuecomment-893833893. For some examples see: https://github.com/rust-lang/rust/pull/87580#issuecomment-894299249

Stabilize `UnsafeCell::raw_get()`

2021-08-31T21:44:13+00:00

Auto merge of #87921 - kellerkindt:master, r=kennytm

2021-08-28T23:39:02+00:00

Add Saturating type (based on Wrapping type) Tracking #87920 ### Unresolved Questions - [x] ~`impl Div for Saturating` falls back on inner integer division - which seems alright?~ - [x] add `saturating_div`? (to respect division by `-1`) - [x] There is no `::saturating_shl` and `::saturating_shr`. (How to) implement `Shl`, `ShlAssign`, `Shr` and `ShrAssign`? - [naively](3f7d2ce28f8cf4dec56bf65fa2e6da0cf329ec55) - [x] ~`saturating_neg` is only implemented on [signed integer types](https://doc.rust-lang.org/std/?search=saturating_n)~ - [x] Is the implementation copied over from the `Wrapping`-type correct for `Saturating`? - [x] `Saturating::rotate_left` - [x] `Saturating::rotate_right` - [x] `Not` - [x] `BitXorOr` and `BitXorOrAssign` - [x] `BitOr` and `BitOrAssign` - [x] `BitAnd` and `BitAndAssign` - [x] `Saturating::swap_bytes` - [x] `Saturating::reverse_bits`

Add doctests to and fix saturating_div for signed integer types

2021-08-19T09:07:29+00:00

Constified `Default` implementations

2021-08-17T07:15:54+00:00

The libs-api team agrees to allow const_trait_impl to appear in the standard library as long as stable code cannot be broken (they are properly gated) this means if the compiler teams thinks it's okay, then it's okay. My priority on constifying would be: 1. Non-generic impls (e.g. Default) or generic impls with no bounds 2. Generic functions with bounds (that use const impls) 3. Generic impls with bounds 4. Impls for traits with associated types For people opening constification PRs: please cc me and/or oli-obk.

feature gate doc(primitive)

2021-08-16T05:41:16+00:00

Add Saturating type (based on Wrapping type)

2021-08-10T17:27:01+00:00

Implement modern Windows arg parsing

2021-08-08T21:11:30+00:00

As derived from extensive testing of `argv` in a C/C++ application. Co-Authored-By: Jane Lusby

Auto merge of #86879 - YohDeadfall:stabilize-vec-shrink-to, r=dtolnay

2021-08-08T19:37:02+00:00

Stabilize Vec::shrink_to This PR stabilizes `shrink_to` feature and closes the corresponding issue. The second point was addressed already, and no `panic!` should occur. Closes #56431.

Auto merge of #87408 - kornelski:try_reserve_error, r=yaahc

2021-08-07T01:26:15+00:00

Hide allocator details from TryReserveError I think there's [no need for TryReserveError to carry detailed information](https://github.com/rust-lang/rust/issues/48043#issuecomment-825139280), but I wouldn't want that issue to delay stabilization of the `try_reserve` feature. So I'm proposing to stabilize `try_reserve` with a `TryReserveError` as an opaque structure, and if needed, expose error details later. This PR moves the `enum` to an unstable inner `TryReserveErrorKind` that lives under a separate feature flag. `TryReserveErrorKind` could possibly be left as an implementation detail forever, and the `TryReserveError` get methods such as `allocation_size() -> Option` or `layout() -> Option` instead, or the details could be dropped completely to make try-reserve errors just a unit struct, and thus smaller and cheaper.