You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksey Demakov (Jira)" <ji...@apache.org> on 2022/09/16 10:44:00 UTC

[jira] [Comment Edited] (IGNITE-17696) C++ coding conventions for ignite-3

    [ https://issues.apache.org/jira/browse/IGNITE-17696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605767#comment-17605767 ] 

Aleksey Demakov edited comment on IGNITE-17696 at 9/16/22 10:43 AM:
--------------------------------------------------------------------

During person-to-person conversations some team mates advocate for fully embracing the naming style of the C++ standard library.


was (Author: JIRAUSER290461):
Some team mates advocate for fully embracing the naming style of the C++ standard library.

> C++ coding conventions for ignite-3
> -----------------------------------
>
>                 Key: IGNITE-17696
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17696
>             Project: Ignite
>          Issue Type: Improvement
>          Components: platforms
>    Affects Versions: 3.0.0-alpha6
>            Reporter: Aleksey Demakov
>            Assignee: Aleksey Demakov
>            Priority: Minor
>             Fix For: 3.0.0-alpha6
>
>
> Establish common style for C++ code in Apache Ignite 3. The suggested approach is as follows:
>  * the C++ code style should resemble the Java style for consistency;
>  * for things that are specific to C++ or break C++ industry-established practices too violently the rules will be settled one by one and described in a MD document in the repo.
> A clang-format file will be provided for automatic indentation of the code.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)