Fix cargo doc warnings (#4794)

This commit is contained in:
Rushmore Mushambi 2024-09-17 13:37:50 +01:00 committed by GitHub
parent c173cd9325
commit 0e8036981e
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -7,21 +7,21 @@
//! # Implementation Details
//!
//! There are a bunch of common patterns for which this module has some confinence functions.
//! - Whenever only one token can be next you should use the [`expected!`] macro. This macro
//! - Whenever only one token can be next you should use the `expected!` macro. This macro
//! ensures that the given token type is next and if not returns a parser error.
//! - Whenever a limited set of tokens can be next it is common to match the token kind and then
//! have a catch all arm which calles the macro [`unexpected!`]. This macro will raise an parse
//! have a catch all arm which calles the macro `unexpected!`. This macro will raise an parse
//! error with information about the type of token it recieves and what it expected.
//! - If a single token can be optionally next use [`Parser::eat`] this function returns a bool
//! depending on if the given tokenkind was eaten.
//! - If a closing delimiting token is expected use [`Parser::expect_closing_delimiter`]. This
//! - If a closing delimiting token is expected use `Parser::expect_closing_delimiter`. This
//! function will raise an error if the expected delimiter isn't the next token. This error will
//! also point to which delimiter the parser expected to be closed.
//!
//! ## Far Token Peek
//!
//! Occasionally the parser needs to check further ahead than peeking allows.
//! This is done with the [`Parser::peek_token_at`] function. This function peeks a given number
//! This is done with the `Parser::peek_token_at` function. This function peeks a given number
//! of tokens further than normal up to 3 tokens further.
//!
//! ## WhiteSpace Tokens