Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
We have a number of spoken and unspoken guidelines around argument passing – some of them are codified in the Google style guide while others (e.g. use of smart pointers as function arguments) are applied via convention and enforced in code reviews.
I propose to add a section to make each case explicit so that our code can become more hygienic and our code reviews less intense
Attachments
Issue Links
- is related to
-
ARROW-13553 [Doc] Add guidelines for code reviews
- Resolved