Fixing a mismatched square bracket typo in src/libstd/slice.rs #14533
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| @@ -38,7 +38,7 @@ These traits include `ImmutableVector`, and `MutableVector` for the `&mut [T]` | |||
| case. | |||
|
|
|||
| An example is the method `.slice(a, b)` that returns an immutable "view" into | |||
| a vector or a vector slice from the index interval `[a, b)`: | |||
| a vector or a vector slice from the index interval `[a, b]`: | |||
There was a problem hiding this comment.
This isn't a typo. Conventionally, the notation [ means "inclusive" and the ) means "exclusive". I.e. [a,b] is {a, a+1, ..., b-1, b} while [a,b) is just {a, a+1, ..., b-1}.
The latter is exactly the behaviour that .slice has.
(I'm going to close, but thanks for reading our docs closely and taking the time to submit a patch! ❤️ )
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Jun 5, 2023
… r=Veykril feat: make inlay hints insertable Part of rust-lang#13812 This PR implements text edit for inlay hints. When an inlay hint contain text edit, user can "accept" it (e.g. by double-clicking in VS Code) to make the hint actual code (effectively deprecating the hint itself). This PR does not implement auto import despite the original request; text edits only insert qualified types along with necessary punctuation. I feel there are some missing pieces to implement efficient auto import (in particular, type traversal function with early exit) so left it for future work. Even without it, user can use `replace_qualified_name_with_use` assist after accepting the edit to achieve the same result. I implemented for the following inlay hints: - top-level identifier pattern in let statements - top-level identifier pattern in closure parameters - closure return type when its has block body One somewhat strange interaction can be observed when top-level identifier pattern has subpattern: text edit inserts type annotation in different place than the inlay hint. Do we want to allow it or should we not provide text edits for these cases at all? ```rust let a /* inlay hint shown here */ @ (b, c) = foo(); let a @ (b, c) /* text edit inserts types here */ = foo(); ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixing a small typo in the documentation for
src/libstd/slice.rs