-
Notifications
You must be signed in to change notification settings - Fork 581
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multi-line vs single-line method and class constructor declarations and invocations #58
Comments
How about if it requires more than two lines, one arg per line. If it fits in two lines, just fit them in two lines? That's what I personally do. |
@rxin and @jkbradley, can I open a PR for describing it? Roughly like:
I think I can quickly do this if we are okay with ^. |
sure - sounds good. |
Sounds good to me |
@jkbradley, this is fixed in #64 :-) |
Apache Spark (especially what I've seen of MLlib) and the current Scala style guide differ on one item: Should multiline method and class constructor invocations be written with 1 arg per line or multiple args per line?
Spark mostly uses multiple args per line (for invocation, not for declarations). The current Scala style guide says to put 1 arg per line: See "Methods with Numerous Arguments" here: http://docs.scala-lang.org/style/indentation.html
Can we add our standard to this doc?
E.g.:
The text was updated successfully, but these errors were encountered: