Alex Thottunkel
- Total activity 2329
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 1
- Subscriptions 1176
Articles
Recent activity by Alex Thottunkel Sort by recent activity-
The code contains paragraphs having the same name
Why you should care Paragraphs having the same name is ambigous, and should be strongly avoided. How we detect CAST Highlight counts one occurrence each time a paragraph having the same name than...
-
The code contains too many bad area A usages
Why you should care In a cobol file, area A (the first four columns) are reserved for divions, sections names, paragraph names and level 01 data declaration. How we detect CAST Highlight counts o...
-
Optional property declarations should use '?' syntax
Why you should care In TypeScript there are several ways to declare an optional property, i.e. a property which might be missing from an object: adding "| undefined" in the property type or adding...
-
Errors should not be created without being thrown
Why you should care Creating a new Error without actually throwing it is useless and is probably due to a mistake. How we detect CAST Highlight counts one occurrence each time 'throw' is not used...
-
Avoid explicit type when it can be inferred from literal value affected
Why you should care For code readability purpose, if a property initializer is a scalar value or the return type can be clearly inferred from the body then it can be omitted. How we detect CAST H...
-
Avoid structures initializations with unamed fields
Why you should care You should almost always specify field names when initializing structs. This is now enforced by go vet. How we detect CAST Highlight counts one occurrence each time a struct f...
-
Avoid self-assigned variables
Why you should care There is no reason to re-assign a variable to itself. Either this statement is redundant and should be removed, or the re-assignment is a mistake and some other value or variab...
-
Avoid binary operators with identical members
Why you should care Using the same value on either side of a binary operator is almost always a mistake. In the case of logical operators, it is either a copy/paste error and therefore a bug, or i...
-
Avoid 'if/else if' & cases statements having the same condition
Why you should care A chain of if/else if statements is evaluated from top to bottom. At most, only one branch will be executed: the first one with a condition that evaluates to true. Therefore, ...
-
Avoid dead code
Why you should care Dead code are instructions that can never be reached. Obvious dead code are instructions that follow unconditional jumps in the same statement block. Dead code could just be d...