rust/src/libcore/ops/mod.rs, branch 1.37.0

libcore => 2018

2019-04-18T05:47:35+00:00

Remove licenses

2018-12-26T04:08:33+00:00

Stabilize `Rc`, `Arc` and `Pin` as method receivers

2018-12-20T06:14:01+00:00

This lets you write methods using `self: Rc`, `self: Arc`, `self: Pin<&mut Self>`, `self: Pin`, and other combinations involving `Pin` and another stdlib receiver type, without needing the `arbitrary_self_types`. Other user-created receiver types can be used, but they still require the feature flag to use. This is implemented by introducing a new trait, `Receiver`, which the method receiver's type must implement if the `arbitrary_self_types` feature is not enabled. To keep composed receiver types such as `&Arc` unstable, the receiver type is also required to implement `Deref` when the feature flag is not enabled. This lets you use `self: Rc` and `self: Arc` in stable Rust, which was not allowed previously. It was agreed that they would be stabilized in #55786. `self: Pin<&Self>` and other pinned receiver types do not require the `arbitrary_self_types` feature, but they cannot be used on stable because `Pin` still requires the `pin` feature.

Various minor/cosmetic improvements to code

2018-12-07T23:53:34+00:00

Replace CoerceSized trait with DispatchFromDyn

2018-11-01T22:16:59+00:00

Rename `CoerceSized` to `DispatchFromDyn`, and reverse the direction so that, for example, you write ``` impl, U> DispatchFromDyn<*const U> for *const T {} ``` instead of ``` impl, U> DispatchFromDyn<*const T> for *const U {} ``` this way the trait is really just a subset of `CoerceUnsized`. The checks in object_safety.rs are updated for the new trait, and some documentation and method names in there are updated for the new trait name — e.g. `receiver_is_coercible` is now called `receiver_is_dispatchable`. Since the trait now works in the opposite direction, some code had to updated here for that too. I did not update the error messages for invalid `CoerceSized` (now `DispatchFromDyn`) implementations, except to find/replace `CoerceSized` with `DispatchFromDyn`. Will ask for suggestions in the PR thread.

Add CoerceSized trait and lang item

2018-11-01T22:15:19+00:00

This trait is more-or-less the reverse of CoerceUnsized, and will be used for object-safety checks. Receiver types like `Rc` will have to implement `CoerceSized` so that methods that use `Rc` as the receiver will be considered object-safe.

Remove all unstable placement features

2018-04-03T09:02:34+00:00

Closes #22181, #27779

Move RangeArguments to {core::std}::ops and rename to RangeBounds

2018-03-29T11:12:49+00:00

These unstable items are deprecated: * The `std::collections::range::RangeArgument` reexport * The `std::collections::range` module.

Move alloc::Bound to {core,std}::ops

2018-03-29T11:12:49+00:00

The stable reexport `std::collections::Bound` is now deprecated. Another deprecated reexport could be added in `alloc`, but that crate is unstable.

Stabilize `inclusive_range` library feature.

2018-03-15T08:58:01+00:00

Stabilize std::ops::RangeInclusive and std::ops::RangeInclusiveTo.