Browse files

tweak post 10

  • Loading branch information...
1 parent b469c54 commit 5c8142dac03b7da9aa89b7318e03bf3e2b50ff34 @lihaoyi committed Jun 15, 2016
Showing with 4 additions and 2 deletions.
  1. +4 −2 post/10 - Strategic Scala Style: Designing
@@ -45,8 +45,7 @@ Apart from the built in data-types, you will end up using data-types defined in
libraries, and find yourself defining your own as your program grows. This post
will explore some considerations and guidelines to remember when designing your
own data-types, and help you sort through the over-abundance of ways that Scala
-lets you model your data. Hopefully this should help you write safer and more
-maintainable Scala programs in future.
+lets you model your data:
- [Opaque or Transparent?](#opaque-or-transparent)
- [Opacity enforces Invariants](#opacity-enforces-invariants)
@@ -78,6 +77,9 @@ Many people who have been using Scala for a while might find much of this
"obvious". Nevertheless, hopefully this post will still be useful in codifying
this "obvious" knowledge for anyone who doesn't find it obvious, and form a
basis for future discussion.
+And on to the first consideration: should you make your data-type opaque or
## Opaque or Transparent?

0 comments on commit 5c8142d

Please sign in to comment.