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
Does it make any sense to have an empty interface (I mean, without any methods defined)?
In my current point of view - empty interfaces do not make sense because these tells nothing about the usage and most likely link to a wrong code architecture after all. If this is not the case of a wrong architecture then chances are very high such cases are linking to premature optimization which is considered a bad practice anyways.
Consider adding the rule that there should not be any empty interfaces, nor other type of abstractions inside the code base.
The text was updated successfully, but these errors were encountered:
Does it make any sense to have an empty interface (I mean, without any methods defined)?
In my current point of view - empty interfaces do not make sense because these tells nothing about the usage and most likely link to a wrong code architecture after all. If this is not the case of a wrong architecture then chances are very high such cases are linking to premature optimization which is considered a bad practice anyways.
Consider adding the rule that there should not be any empty interfaces, nor other type of abstractions inside the code base.
The text was updated successfully, but these errors were encountered: