Skip to content

Conversation

@KseniyaTikhomirova
Copy link
Contributor

No description provided.

Signed-off-by: Tikhomirova, Kseniya <kseniya.tikhomirova@intel.com>
@KseniyaTikhomirova
Copy link
Contributor Author

some extra details can be found here #166927 (comment)

@bader bader changed the title [SYCL] add CodingGuidelines.rst for libsycl [SYCL] Add CodingGuidelines.rst for libsycl Dec 11, 2025
@bader bader requested review from bader and tahonermann December 11, 2025 17:03
classes for LIT tests and that should be excluded from test descovery.

* **File Names in snake case** should be used for all C++ implementation files.
For example files in folders ``include``, ``src``, ``test``, ``utils``,
Copy link
Contributor Author

@KseniyaTikhomirova KseniyaTikhomirova Dec 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

test is an umbrella for all types of tests here. I expect test_e2e and unittests follow the same rule.

Introduction
============

In general ``libsycl`` project adopts LLVM Coding Standards.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A link to LLVM Coding Standards would be helpful here I think to ease user's navigation.

@Fznamznon Fznamznon added the SYCL https://registry.khronos.org/SYCL label Dec 15, 2025
* **Other types (implementation details)** should follow LLVM Coding Standards
and should be declared in camel case.

Name of Files and Folders
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please, use term "directory" instead of "folder".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

SYCL https://registry.khronos.org/SYCL

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants