Skip to content

Commit

Permalink
Auto merge of #335 - reddraggone9:docs-rename, r=BurntSushi
Browse files Browse the repository at this point in the history
Update docs to reflect `at` -> `get` rename

I noticed this while perusing the documentation and ran
```sh
rg '`at`'
```
in the repo to find these four instances. Feels kinda meta.
  • Loading branch information
bors committed Feb 18, 2017
2 parents e2904f8 + 799d333 commit 7dfa895
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
4 changes: 2 additions & 2 deletions src/re_bytes.rs
Original file line number Diff line number Diff line change
Expand Up @@ -246,7 +246,7 @@ impl Regex {
///
/// Here we name the capture groups, which we can access with the `name`
/// method or the `Index` notation with a `&str`. Note that the named
/// capture groups are still accessible with `at` or the `Index` notation
/// capture groups are still accessible with `get` or the `Index` notation
/// with a `usize`.
///
/// The `0`th capture group is always unnamed, so it must always be
Expand Down Expand Up @@ -763,7 +763,7 @@ impl<'r> Iterator for CaptureNames<'r> {
/// index corresponds to the next capture group in the regex. If a capture
/// group is named, then the matched byte string is *also* available via the
/// `name` method. (Note that the 0th capture is always unnamed and so must be
/// accessed with the `at` method.)
/// accessed with the `get` method.)
///
/// Positions returned from a capture group are always byte indices.
///
Expand Down
4 changes: 2 additions & 2 deletions src/re_unicode.rs
Original file line number Diff line number Diff line change
Expand Up @@ -321,7 +321,7 @@ impl Regex {
///
/// Here we name the capture groups, which we can access with the `name`
/// method or the `Index` notation with a `&str`. Note that the named
/// capture groups are still accessible with `at` or the `Index` notation
/// capture groups are still accessible with `get` or the `Index` notation
/// with a `usize`.
///
/// The `0`th capture group is always unnamed, so it must always be
Expand Down Expand Up @@ -901,7 +901,7 @@ impl<'n> Iterator for NamedGroupsIter<'n> {
/// index corresponds to the next capture group in the regex. If a capture
/// group is named, then the matched string is *also* available via the `name`
/// method. (Note that the 0th capture is always unnamed and so must be
/// accessed with the `at` method.)
/// accessed with the `get` method.)
///
/// Positions returned from a capture group are always byte indices.
///
Expand Down

0 comments on commit 7dfa895

Please sign in to comment.