Alex Thottunkel
- Total activity 2325
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 1
- Subscriptions 1186
Articles
Recent activity by Alex Thottunkel Sort by recent activity-
The code contains too many functions not complying with naming conventions
Why you should care Complying with naming conventions make the source code easier to ready and so to maintain. Function names should start with an upper case and should not contain underscores OR ...
-
The code contains too many final artifacts in final classes
Why you should care Unnecessary final modifiers inside final classes should be avoided. Final modifier prevents child classes from overriding a method by prefixing the definition with final. If th...
-
The code contains too many classes that declare __get() without declaring __set()
Why you should care When __get() are declared, __set() shoud be declared as well. How we detect CAST Highlight counts one occurrence each time a __get() is detected in source code without an asso...
-
The code contains too many class names that do not begin with an uppercase letter
Why you should care Complying with naming conventions make the source code easier to ready and so to maintain. Class names should start with an upper case. How we detect CAST Highlight counts one...
-
Force casts should not be used
Why you should care Because force casting (as!) does not perform any type safety validations, it is capable of performing dangerous conversions between unrelated types. When the types are truly un...
-
Prefer to use an expression body for functions whose body consists of a single expression
Why you should care Prefer using an expression body for functions with the body consisting of a single expression. How we detect CAST Highlight counts one occurrence each time a function consisti...
-
Avoid abstract classes without abstract or concrete methods
Why you should care Abstract classes can have public constructors, and this is required in some particular cases. But a public constructor means that the class can be instantiated directly while, ...
-
Use short variable declarations (:=) for variables with default values
Why you should care Short variable declarations (:=) should be used if a variable is being set to some value explicitly. How we detect CAST Highlight counts one occurrence each time a local varia...
-
Avoid naming unused receivers
Why you should care If the receiver of a method is unused, do not give it a name. It's more readable because it's clear that the receiver is not used in method. How we detect CAST Highlight count...
-
Avoid instantiation with new
Why you should care Use &T{} instead of new(T) when initializing struct references so that it is consistent with the struct initialization. How we detect CAST Highlight counts one occurrence each...