Skip to content

Update naming-conventions.md: remove duplications #2016

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

Merged
merged 3 commits into from
Jul 12, 2021
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions _style/naming-conventions.md
Original file line number Diff line number Diff line change
Expand Up @@ -266,7 +266,7 @@ advanced feature in Scala, to be used only by those most well-versed in
its pitfalls. Without care, excessive use of symbolic method names can
easily transform even the simplest code into symbolic soup.

## Constants, Values, Variable and Methods
## Constants, Values and Variable

Constant names should be in upper camel case. Similar to Java's `static final`
members, if the member is final, immutable and it belongs to a package
Expand All @@ -278,10 +278,9 @@ object or an object, it may be considered a constant:

The value: `Pi` in `scala.math` package is another example of such a constant.

Method, Value and variable names should be in lower camel case:
Value and variable names should be in lower camel case:

val myValue = ...
def myMethod = ...
var myVariable

## Type Parameters (generics)
Expand Down