Skip to content

style: use full paths for internal headers in capi/...#313

Open
VDanielEdwards wants to merge 1 commit intomainfrom
dev/refactor/use-full-include-paths-capi
Open

style: use full paths for internal headers in capi/...#313
VDanielEdwards wants to merge 1 commit intomainfrom
dev/refactor/use-full-include-paths-capi

Conversation

@VDanielEdwards
Copy link
Copy Markdown
Member

Subject

Use full paths for internal headers in all sources and headers in SilKit/source/capi/. Rearranges the includes to follow the guidelines in the Google Styleguide for C++. Removes unneccessary includes.

Developer checklist (address before review)

  • Changelog.md updated
  • Prepared update for depending repositories
  • Documentation updated (public API changes only)
  • API docstrings updated (public API changes only)
  • Rebase → commit history clean
  • Squash and merge → proper PR title

@VDanielEdwards VDanielEdwards self-assigned this Apr 24, 2026
@snps-behrens
Copy link
Copy Markdown
Collaborator

Is there any particular reason you chose the google style guide? I have found that using the llvm style guide leads to headers being more self-contained.

Signed-off-by: Daniel Edwards <Daniel.Edwards@vector.com>
@VDanielEdwards VDanielEdwards force-pushed the dev/refactor/use-full-include-paths-capi branch from d46ede3 to dda8abe Compare April 24, 2026 13:13
@VDanielEdwards
Copy link
Copy Markdown
Member Author

Is there any particular reason you chose the google style guide? I have found that using the llvm style guide leads to headers being more self-contained.

No particular reason, it was just the first that came to mind. But I do like the ordering from local -> global as in the LLVM styleguide more than what the Google styleguide suggests.

@MariusBgm would you object to switching the include-order to the LLVM styleguide?

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