Repository navigation
[WS AI] Open source coding rules for C++ and Rust #695
Description
See AI27 discussed in https://github.com/orgs/eclipse-score/discussions/375
Owner: @elfenpiff / @elBoberido
Propose coding rules (for both C++ and Rust) that are applied and traceable in the open source.
Activity
elfenpiff commentedon Mar 17, 2025
Since we will need to maintain C++ and Rust code side by side for the foreseeable future of the project, I propose adopting a C++ style guide that aligns as closely as possible with the default Rust style guide.
Additionally, I suggest strictly adhering to the Rust coding guidelines without deviation, as they are well-established and widely accepted.
Keeping the style guides closely aligned minimizes cognitive load for developers, allowing them to focus on algorithmic challenges—an essential factor, especially for mission-critical code.
I propose the following tools with an initial rule set as a starting point.
Additionally, the codebase shall not allow any compiler warnings, except for
[-Wdeprecated]. This specific warning ensures that developers are informed about deprecated code sections that are available only at a lower criticality level. It enables a smooth transition toward higher criticality by guiding developers to swap to certified implementations when necessary.AlexanderLanin commentedon May 15, 2025
coding rules is process AFAIK
elfenpiff commentedon May 16, 2025
@AlexanderLanin what do you mean with
Could you please elaborate it a bit more.
AlexanderLanin commentedon May 19, 2025
I meant we don't have a clear alignment on who will work on coding rules, but it probably involves the process team.
FScholPer commentedon May 21, 2025
TL-> No clear epic
johannes-esr commentedon Oct 2, 2025
Closed, there are special tickets for coding style and static/dynamic code analysis: