[
https://issues.apache.org/jira/browse/SPARK-6813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596678#comment-14596678
]
Shivaram Venkataraman commented on SPARK-6813:
----------------------------------------------
I think we can start fixing the problems, but lets do the fixes in a few
separate PRs. The first PR can be just be trailing whitespace fixes, the second
one can be line length fixes, other whitespace issues and the third one can be
the rest. Let me know if that sounds good.
> SparkR style guide
> ------------------
>
> Key: SPARK-6813
> URL: https://issues.apache.org/jira/browse/SPARK-6813
> Project: Spark
> Issue Type: New Feature
> Components: SparkR
> Reporter: Shivaram Venkataraman
>
> We should develop a SparkR style guide document based on the some of the
> guidelines we use and some of the best practices in R.
> Some examples of R style guide are:
> http://r-pkgs.had.co.nz/r.html#style
> http://google-styleguide.googlecode.com/svn/trunk/google-r-style.html
> A related issue is to work on a automatic style checking tool.
> https://github.com/jimhester/lintr seems promising
> We could have a R style guide based on the one from google [1], and adjust
> some of them with the conversation in Spark:
> 1. Line Length: maximum 100 characters
> 2. no limit on function name (API should be similar as in other languages)
> 3. Allow S4 objects/methods
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
