You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a question I am curious to ask since I first viewed your repository, hope this is the right place to ask so everyone can benefit from it.
Going through many of your functions, I have found inconsistencies with respect to usual R coding conventions, such as Google's R Style Guide. To be fair, while submitting new pull requests, I have sometimes omitted to apply them myself in order to avoid the "whitespace problem".
This is a subjective topic, but I would like to put it in what may hopefully become constructive. My fundamental question is: do you have a favorite coding style that may be a guideline to consistently enforce across the package? If yes, would you like to share it?
Chiefly, I am interested in this because it may be the case you actually prefer new code to be written that way, but comments about what a contributor is allowed to (occasionally) do with the existing code will be much appreciated too. (As for now I am not proposing such big changes.)
The text was updated successfully, but these errors were encountered:
Hi!
There is a question I am curious to ask since I first viewed your repository, hope this is the right place to ask so everyone can benefit from it.
Going through many of your functions, I have found inconsistencies with respect to usual
R
coding conventions, such as Google's R Style Guide. To be fair, while submitting new pull requests, I have sometimes omitted to apply them myself in order to avoid the "whitespace problem".This is a subjective topic, but I would like to put it in what may hopefully become constructive. My fundamental question is: do you have a favorite coding style that may be a guideline to consistently enforce across the package? If yes, would you like to share it?
Chiefly, I am interested in this because it may be the case you actually prefer new code to be written that way, but comments about what a contributor is allowed to (occasionally) do with the existing code will be much appreciated too. (As for now I am not proposing such big changes.)
The text was updated successfully, but these errors were encountered: