Skip to content

Commit 558ce5e

Browse files
formidojosevalim
authored andcommitted
Fix typo (#730)
Could be also fixed by: "Now all data types (including structs) in which we have not implemented the Blank protocol will be considered non-blank.
1 parent 81e725c commit 558ce5e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

getting-started/protocols.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -159,7 +159,7 @@ defimpl Blank, for: Any do
159159
end
160160
```
161161

162-
Now all data types (including structs) that we have not implemented the `Blank` protocol will be considered non-blank. In contrast to `@derive`, falling back to `Any` is opt-out: all data types get a pre-defined behaviour unless they provide their own implementation of the protocol. Which technique is best depends on the use case but, given Elixir developers prefer explicit over implicit, you may see many libraries pushing towards the `@derive` approach.
162+
Now all data types (including structs) that have not implemented the `Blank` protocol will be considered non-blank. In contrast to `@derive`, falling back to `Any` is opt-out: all data types get a pre-defined behaviour unless they provide their own implementation of the protocol. Which technique is best depends on the use case but, given Elixir developers prefer explicit over implicit, you may see many libraries pushing towards the `@derive` approach.
163163

164164
## Built-in protocols
165165

0 commit comments

Comments
 (0)