Clarify that core::range ranges do not have special syntax

[shepmaster]

r? @tgross35

[rustbot]

tgross35 is currently at their maximum review capacity.
They may take a while to respond.

[shepmaster]

It's probably worth calling out a few things that seemed suspicious but that I didn't change...

These doctests seem to be testing the legacy syntax, unless I misunderstand how the standalone_crate modifier works:

• rust/library/core/src/range.rs

  Lines 587 to 589 in c771f6e

  	/// for i in ..=5 {
  	/// // ...
  	/// }

• rust/library/core/src/range.rs

  Lines 596 to 602 in c771f6e

  	/// let arr = [0, 1, 2, 3, 4];
  	/// assert_eq!(arr[ .. ], [0, 1, 2, 3, 4]);
  	/// assert_eq!(arr[ .. 3], [0, 1, 2 ]);
  	/// assert_eq!(arr[ ..=3], [0, 1, 2, 3 ]); // This is a `RangeToInclusive`
  	/// assert_eq!(arr[1.. ], [ 1, 2, 3, 4]);
  	/// assert_eq!(arr[1.. 3], [ 1, 2 ]);
  	/// assert_eq!(arr[1..=3], [ 1, 2, 3 ]);

I didn't change any of the mentions about "2-tuple of Bound<&T>" as these are a bit more nuanced and I just wanted to clear up the high-level confusion.

• rust/library/core/src/range.rs

  Line 188 in c771f6e

  /// consider using the `RangeBounds` impl for a 2-tuple of [`Bound<&T>`][Bound],

There's one usage of doc(alias. I don't know why it's only applied to one type in this file, but it should probably be consistent (and I'd vote for "consistently not present in this file, yet").

• rust/library/core/src/range.rs

  Line 607 in c771f6e

  #[doc(alias = "..=")]

[shepmaster]

/cc @pitaj @Mark-Simulacrum

[tgross35]

@bors r+ rollup

View changes since this review

[rust-bors]

📌 Commit eef4363 has been approved by tgross35

It is now in the queue for this repository.

[tgross35]

It's probably worth calling out a few things that seemed suspicious but that I didn't change...

Agreed with everything you mention here, I assume the original docs were likely copied from core::ops, possibly with the thought that these types would stabilize at the same time as the new syntax rather than before. Seems like there is room for further improvement, but also agreed that you got the most pressing thing here.

[rustbot]

beta backport approved as per compiler team on Zulip. A backport PR will be authored by the release team at the end of the current development cycle. Backport labels are handled by them.