Skip to content

Commit c3dce04

Browse files
authored
Update docs: refining use of word "parameter" vs "argument"
An excellent clarification on when to use "parameters" vs "arguments": https://stackoverflow.com/questions/156767/whats-the-difference-between-an-argument-and-a-parameter?page=1&tab=scoredesc#tab-top
1 parent d9ebf0c commit c3dce04

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

_style/naming-conventions.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -363,10 +363,10 @@ going beyond a few lines. Few local names are used (including
363363
parameters), and so there is no need to contrive long, descriptive
364364
names. This convention substantially improves the brevity of most Scala
365365
sources. This in turn improves readability, as most expressions fit in
366-
one line and the arguments to methods have descriptive type names.
366+
one line and the parameters for methods have descriptive type names.
367367

368368
This convention only applies to parameters of very simple methods (and
369369
local fields for very simply classes); everything in the public
370-
interface should be descriptive. Also note that the names of arguments
370+
interface should be descriptive. Also note that the names of parameters
371371
are now part of the public API of a class, since users can use named
372372
parameters in method calls.

0 commit comments

Comments
 (0)