On Thu, 25 Oct 2012 20:28:49 +0200, Josh Berry <[email protected]> wrote:
On Thu, Oct 25, 2012 at 10:58 AM, Fabrizio Giudici
<[email protected]> wrote:
2. Option is not a Scala thing, is a micro-design pattern. I could like
it
or not, but being a pattern I think I shouldn't see it at all, or see
in all
the languages I like.
I think this is a key misunderstanding. One I mostly share. Option
is not a micro design pattern any more than String is. It is a common
type that is shared in many languages. Same as List or Map. Maybe
I'm placing more distinction on this than is necessary, but it is
important.
It's a type, but you can't compare it to a String. String is a type born
to model a certain kind of stuff. Sure I can't imagine a different,
practical way to represent text. Option is a type born to support some
constructs, such as avoiding null.
Can you imagine working with a language where String was
implemented vastly differently than the way it is commonly done? (But
still called String.)
Of course, I however agree with this statement, Option is well defined
from a conceptual point of view and should be the same thing everywhere.
--
Fabrizio Giudici - Java Architect @ Tidalwave s.a.s.
"We make Java work. Everywhere."
http://tidalwave.it/fabrizio/blog - [email protected]
--
You received this message because you are subscribed to the Google Groups "Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
