New answers tagged scala
I would definately go with the "overkill" solution: have a public project for the api, and a separate project for implementation. com/ example/ framework/ api/ implementation/ implementation of course will have a dependency on api. I see 2 advantages: It will be easy for you to keep your public api interface clean. No classes ...
A better question here would be why Haskell's option type is called Maybe. ML's option type is probably the grandaddy of all option types, and it's called option. In any case, this is a terminological question, so it's not going to have a principled answer. The people who picked the name in Haskell liked it better, that's it.
Top 50 recent answers are included