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
I realize that this is a controversial item and that there are already a few inconclusive discussions about it, but I hope that my question may have a clear answer.
Basically, I would like it clarified whether the intended reading of this guideline is
Avoid pairs of trivial getters and trivial setters
or
Avoid trivial getters and avoid trivial setters
and if it's the latter, why?
It seems to me that it is perfectly reasonable to have a trivial getter if the setter is non-trivial (or not present). This does not appear to contradict the reasoning in the item in any way. I'm even thinking that maybe the most direct way to communicate the intent would be
Avoid trivial setters
wouldn't it?
The text was updated successfully, but these errors were encountered:
I realize that this is a controversial item and that there are already a few inconclusive discussions about it, but I hope that my question may have a clear answer.
Basically, I would like it clarified whether the intended reading of this guideline is
or
and if it's the latter, why?
It seems to me that it is perfectly reasonable to have a trivial getter if the setter is non-trivial (or not present). This does not appear to contradict the reasoning in the item in any way. I'm even thinking that maybe the most direct way to communicate the intent would be
wouldn't it?
The text was updated successfully, but these errors were encountered: