Skip to content

fix: removes unused variable - #63

Closed
vulder wants to merge 1 commit into
mainfrom
fix/gcc-build-error
Closed

fix: removes unused variable#63
vulder wants to merge 1 commit into
mainfrom
fix/gcc-build-error

Conversation

@vulder

@vulder vulder commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Removes unused variable detected by gcc-16 and onward.

@vulder
vulder requested a review from EnriqueParodi as a code owner July 6, 2026 18:02
EnriqueParodi added a commit that referenced this pull request Aug 19, 2026
The new nightly clang-tidy job runs over the whole tree; this clears every
finding its first full run reported, so the job is green from night one.
Where a check is wrong or the code is deliberate, the waiver is written
next to the code together with its reason. It also carries the unused
variable removal from #63, which gcc-16 reports as an error.

Co-authored-by: Florian Sattler <florian.sattler@airbus.com>
@EnriqueParodi

Copy link
Copy Markdown
Collaborator

Folded into #86, which carries it with attribution (Co-authored-by: Florian Sattler). The clang-tidy cleanup touches the same area and the CI stack lands as one unit, so keeping this as a separate PR would have meant rebasing it behind the whole stack for a one-line change.

Closing here; the change itself is unchanged from what you wrote. The fix/gcc-build-error branch is left in place — delete it whenever you like.

EnriqueParodi added a commit that referenced this pull request Aug 19, 2026
The new nightly clang-tidy job runs over the whole tree; this clears every
finding its first full run reported, so the job is green from night one.
Where a check is wrong or the code is deliberate, the waiver is written
next to the code together with its reason. It also carries the unused
variable removal from #63, which gcc-16 reports as an error.

Co-authored-by: Florian Sattler <florian.sattler@airbus.com>
EnriqueParodi added a commit that referenced this pull request Aug 19, 2026
The new nightly clang-tidy job runs over the whole tree; this clears every
finding its first full run reported, so the job is green from night one.
Where a check is wrong or the code is deliberate, the waiver is written
next to the code together with its reason. It also carries the unused
variable removal from #63, which gcc-16 reports as an error.

Co-authored-by: Florian Sattler <florian.sattler@airbus.com>
EnriqueParodi added a commit that referenced this pull request Aug 19, 2026
The new nightly clang-tidy job runs over the whole tree; this clears every
finding its first full run reported, so the job is green from night one.
Where a check is wrong or the code is deliberate, the waiver is written
next to the code together with its reason. It also carries the unused
variable removal from #63, which gcc-16 reports as an error.

Co-authored-by: Florian Sattler <florian.sattler@airbus.com>
EnriqueParodi added a commit that referenced this pull request Aug 20, 2026
The new nightly clang-tidy job runs over the whole tree; this clears every
finding its first full run reported, so the job is green from night one.
Where a check is wrong or the code is deliberate, the waiver is written
next to the code together with its reason. It also carries the unused
variable removal from #63, which gcc-16 reports as an error.

Co-authored-by: Florian Sattler <florian.sattler@airbus.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants