HIGHLIGHT Product Documentation

This documentation is for reference only. Original Highlight Product Documentation is available at https://doc.casthighlight.com/

• Too many uses of ternary operators can increase costs
• Too many class implementations can increase costs
• Too many class definitions can cause agility issues
• Constructors with a return value can be unproductive in PHP
• While Loops are more productive than For Loops
• Having empty statements can be unproductive in PHP
• Too many functions with default value parameters are unproductive
• Having an assignment to "this" can be unproductive
• Using "instanceOf" causes Production Risk
• Too many global variables can be unproductive
• Switch cases without ending breaks are hard to understand
• Memory leaks in C++ is a huge production risk
• Inconditional branches are unproductive in C++
• Too many classes with missing destructors can be unproductive
• Too many classes with missing constructors can be risky
• Incorrect dynamic class definition can be non-resilient
• Macro definitions cause resiliency issues
• Classes with missing destructor declarations can be unproductive
• Single quote strings keeps code consistent and productive
• Array literals are less risky than Array constructors in JavaScript
• Too many "for in" loops is risky
• Missing Semicolons in JavaScript can be very unproductive
• Simplified Syntax can be unproductive in KSH
• Leaving arguments unchecked hinders progress
• Having too much Spaghetti Code can be risky
• No explicit EXIT instruction in last statement in KSH can be risky
• Methods as functions tend to be unproductive
• Explicit return in __init__ is Unproductive
• Magic Methods in Python can be Risky
• Having + for list concatenation