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

Francois Saint-Jacques commented on ARROW-2981:
-----------------------------------------------

There's a lot of warning in the actual clang-tidy script, should we fix all of 
them?


{code}
      1 [google-global-names-in-headers]
      1 [readability-redundant-member-init]
      2 [google-readability-braces-around-statements]
      2 [modernize-use-bool-literals]
      3 [readability-non-const-parameter]
      6 [modernize-redundant-void-arg]
      7 [readability-inconsistent-declaration-parameter-name]
      9 [modernize-deprecated-headers]
     10 [modernize-use-auto]
     11 [google-readability-namespace-comments]
     13 [readability-simplify-boolean-expr]
     41 [modernize-use-noexcept]
     53 [readability-implicit-bool-conversion]
     75 [google-default-arguments]
     76 [clang-diagnostic-error]
     76 [clang-diagnostic-unused-command-line-argument]
     82 [readability-braces-around-statements]
     97 [modernize-use-using]
    100 [modernize-use-override]
    107 [modernize-use-default-member-init]
    110 [google-readability-todo]
    159 [google-explicit-constructor]
    167 [readability-else-after-return]
    205 [modernize-use-nullptr]
    296 [readability-named-parameter]
    391 [modernize-use-equals-default]
    442 [modernize-use-equals-delete]
    617 [google-runtime-references]
   1047 [readability-avoid-const-params-in-decls]
{code}


> [C++] Support scripts / documentation for running clang-tidy on codebase
> ------------------------------------------------------------------------
>
>                 Key: ARROW-2981
>                 URL: https://issues.apache.org/jira/browse/ARROW-2981
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>            Reporter: Wes McKinney
>            Priority: Major
>             Fix For: 0.11.0
>
>
> Related to ARROW-2952, ARROW-2980



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to