Re: [scala-language] The cake’s problem, dotty des ign and the approach to modularity.

> (Unfortunately, due to a lack of a really
> robust way to specify logical dependencies, you often need the source code
> to the library anyway so you know what is safe to override alone, what must
> be overridden in pairs, etc.).

er, hmmm, isn't that part of the larger indictment of inheritance
(subclassing+subtyping all in one)? Vs. e.g. traits, right? That kind
of inheritance seems to be viewed by most folks I think I respect well
enough, to be something basically evil. Maybe a path that seems paved
with good intentions, but turns into a cesspit all too soon. No?

-- 
You received this message because you are subscribed to the Google Groups "scala-language" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.