Scott McMurray c20ad72323 Stabilize Range[Inclusive]::is_empty ...

I would like to propose these two simple methods for stabilization:
- Knowing that a range is exhaused isn't otherwise trivial
- Clippy would like to suggest them, but had to do extra work to disable that path <https://github.com/rust-lang/rust-clippy/issues/3807> because they're unstable
- These work on `PartialOrd`, consistently with now-stable `contains`, and are thus more general than iterator-based approaches that need `Step`
- They've been unchanged for some time, and have picked up uses in the compiler
- Stabilizing them doesn't block any future iterator-based is_empty plans, as the inherent ones are preferred in name resolution

2020-08-24 13:20:25 -07:00

..

fmt

…

hash

…

num

also reduce some libcore test iteration counts

2020-07-31 11:56:08 +02:00

alloc.rs

…

any.rs

…

array.rs

Add drop check test & MaybeUninit::first_ptr_mut

2020-08-13 03:51:08 +00:00

ascii.rs

enable align_to tests in Miri

2020-08-19 10:41:51 +02:00

atomic.rs

…

bool.rs

…

cell.rs

…

char.rs

…

clone.rs

…

cmp.rs

…

intrinsics.rs

…

iter.rs

Use min_specialization in libcore

2020-08-19 20:08:02 +01:00

lazy.rs

Make OnceCell<T> transparent to dropck

2020-08-18 00:34:54 +02:00

lib.rs

Stabilize Range[Inclusive]::is_empty

2020-08-24 13:20:25 -07:00

manually_drop.rs

…

mem.rs

…

nonzero.rs

…

ops.rs

…

option.rs

…

pattern.rs

…

ptr.rs

enable align_to tests in Miri

2020-08-19 10:41:51 +02:00

result.rs

Update tests

2020-07-31 02:44:29 +00:00

slice.rs

enable align_to tests in Miri

2020-08-19 10:41:51 +02:00

str_lossy.rs

…

str.rs

…

time.rs

…

tuple.rs

…