docs(cpp/deque): add .back() term entry #7727
Open
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
…ebyte\n\n- New term: deque::back() at content/cpp/concepts/deque/terms/back/back.md\n- Includes description, Syntax, Example with output, and Codebyte example\n- Follows Docs term template, content standards, and style guide\n- Notes undefined behavior when called on empty deque
|
|
|
Hey @HackersSpirit, please sign the CLA |
3 tasks
mamtawardhani
approved these changes
Oct 13, 2025
mamtawardhani
added
c++
|
@HackersSpirit please sign the CLA otherwise we'll have to close this PR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary: Add a new C++ term entry for deque::back().
Includes:
Description
Syntax (pseudo block + details)
Example (cpp) with Output (shell)
Codebyte Example (codebyte/cpp)
Notes:
First mention bolded
Added note on undefined behaviour for empty deque
Follows term-entry-template, content-standards, and style-guide