Skip to content

Commit 2367300

Browse files
authored
Update naming-conventions.md
1 parent 290b5d6 commit 2367300

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

lib/elixir/pages/references/naming-conventions.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -107,12 +107,10 @@ Type checks and other boolean checks that are allowed in guard clauses are named
107107

108108
Examples: `Integer.is_even/1`, `is_list/1`
109109

110-
These functions and macros follow the Erlang convention of an `is_` prefix, instead of a trailing question mark, precisely to indicate that they are allowed in guard clauses.
110+
These functions and macros follow the Erlang convention of an `is_` prefix, instead of a trailing question mark, precisely to indicate that they are allowed in guard clauses. Type checks that are not valid in guard clauses do not follow this convention, such as `Keyword.keyword?/1`.
111111

112112
A trailing question mark should not be used in combination with the `is_` prefix.
113113

114-
Note that type checks that are not valid in guard clauses do not follow this convention. For example: `Keyword.keyword?/1`.
115-
116114
## Special names
117115

118116
Some names have specific meaning in Elixir. We detail those cases below.

0 commit comments

Comments
 (0)