Comments 2
I expect an article proposing separating behavior from data types, to discuss abstractions, interface vs implementation, open-closed principle, breaking changes. The only point I see it this article is that one may want to have an operation which involves multiple data types and doesn't fit just one of the data type abstractions.
Probably in the future I am going to cover those subjects as well, thanks for the feedback. Here I just wanted to make the point that it’s not right (in my opinion) to combine type with its functionality, because function’s arguments must be equally considered as just a parts of one process which a function represents.
Sign up to leave a comment.
Data Type Should Not Be Considered As a Source of Its Behaviour