You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@xeno-by said (edited on Feb 1, 2014 2:03:41 AM UTC):
While classifying symbols for #8220 it would be nice to think about this behavior once again. Do we want abstract methods generated for vals to be treated as vals? Do we not? Or maybe we should eschew this classification altogether and come up with something better (i.e. classes - objects - fields - methods - type members or even subdivide methods into methods - getters - setters)?
I would expect "filterNot (_.isVal)" to filter out all these things which present themselves as vals.
The text was updated successfully, but these errors were encountered: