You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Ben Kietzman (Jira)" <ji...@apache.org> on 2021/08/18 16:49:00 UTC

[jira] [Commented] (ARROW-13414) [C++] Review/apply guidelines for comment tags

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

Ben Kietzman commented on ARROW-13414:
--------------------------------------

Worth noting: cpplint includes a check for TODOs which is currently disabled https://github.com/bkietz/arrow/blob/fc8a51387fc7810c1d32ee7ece0c9eae02b618c0/cpp/build-support/run_cpplint.py#L37 

> [C++] Review/apply guidelines for comment tags
> ----------------------------------------------
>
>                 Key: ARROW-13414
>                 URL: https://issues.apache.org/jira/browse/ARROW-13414
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>            Reporter: Eduardo Ponce
>            Priority: Minor
>             Fix For: 6.0.0
>
>
> The google style guide describes best practices for source code comments including for [TODO comments|https://google.github.io/styleguide/cppguide.html#TODO_Comments]. Nevertheless, Arrow C++ code contains comments with custom tags (*TODO*, *NOTE*, *N.B.*, *XXX*) which are used with varying styles and do not have an explicit guideline on their use/meaning.
> It would be good to establish guidelines for allowed custom tags (if any) and their use case.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)