len() as upper boundary makes code less readable

CostSoftware AgilityCode Readability

len() as upper boundary makes code less readable

This code insight shows that
Python tries to make the task of slicing lists and numpy.arrays as convenient as possible.

If one needs a slice which reaches till the end of the object the upper boundary can be left empty.

When negative numbers are used the indexing will start at the end.

5362

Why you should care


Business Impacts

It is recommended to avoid these in order to ensure the code is more readable and cost effective.

Cost

CAST recommendations

References

Quantified code :

https://www.quantifiedcode.com/knowledge-base/readability/Omit%20%60len%28%29%60%20as%20upper%20boundary/27a0ZNa7

https://www.quantifiedcode.com/knowledge-base/Omit%20%60len()%60%20for%20indexing/slicing/49Cho3Zk

5362

About CAST and Highlight’s Code Insights

Over the last 25 years, CAST has leveraged unique knowledge on software quality measurement by analyzing thousands of applications and billions of lines of code. Based on this experience and community standards on programming best practices, Highlight implements hundreds of code insights across 15+ technologies to calculate health factors of a software.

See featuresHow it works