@dibblego isn't it more that you should non-trivial initialisation of said vals, particularly if they depend on abstract stuff?
Anyone up for a blog post debunking the silly idea that you shouldn't use val in #scala traits (and it eliminates lots of decent code)?
-
-
-
@jedws Yes it is true that there are initialisation issues to consider, but that does not mean you eliminate ability for decent code.
End of conversation
New conversation -
-
-
@dibblego I would love to see such a post; I don't think either side of the argument for/against val in traits has been clearly articulated. -
@mergeconflict I normally ignore misguided principles, but this one has such a huge practical cost. Even intellij warnings annoy me over it. - Show replies
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@dibblego My 1st stab: declare abstr.val in trait =(perfectly)OK; refer to this abstr.val from a val = NOT OK#scala https://github.com/rintcius/scala-stuff/blob/master/src/test/scala/nl/rintcius/poc/ValInTraitSpec.scala … -
@rintcius yes this is a reasonable principle. We have to destroy the broken principle too, due to its high practical cost. - Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.