Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[dcl.attr.noreturn]/3 Replace `[[noreturn]]` with `noreturn` for consistency

Open Beginner friendly
#9,348 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
85/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
cpp, tex
Domain
documentation

Research direction

The issue points to a specific section [dcl.attr.noreturn]/3 in the C++ standard draft. Look at the TeX source file for that section, likely in a .tex file within the repository. Compare the formatting of [[noreturn]] with other attribute references in the same clause to ensure consistency. The change is a simple text replacement from [[noreturn]] to noreturn as per the grammar in [dcl.attr].

Written by the indexing model from the issue text.

Description

P2-Bug

[dcl.attr.noreturn]/3 says

Recommended practice: Implementations should issue a warning if a function marked [[noreturn]] might return. The value of a has-attribute-expression for the noreturn attribute should be 0 unless the implementation can issue such warnings.

It uses double brackets to enclose the attribute.

However, the enclosing double brackets are not used in all other similar contexts in [dcl.attr].

Dominant language
TeX
Stars
221
Forks
813
Avg merge
17h 45m
Merged PRs (30d)
34

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cplusplus/draft

All issues in cplusplus/draft

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.