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
{{ message }}
This repository has been archived by the owner on Mar 25, 2021. It is now read-only.
Users who come from a Java-style OO language may wrap their utility functions in an extra class, instead of putting them at the top level. In this case, they probably should instead use inner namespaces or remove the nesting altogether.
I propose a no-static-only-class rule that warns on
a class
with only static members
which does not:
extend another class or implement an interface, or
have a non-empty constructor
The text was updated successfully, but these errors were encountered:
Users who come from a Java-style OO language may wrap their utility functions in an extra class, instead of putting them at the top level. In this case, they probably should instead use inner namespaces or remove the nesting altogether.
I propose a
no-static-only-class
rule that warns onThe text was updated successfully, but these errors were encountered: