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
Similar to issue #32 - showing the number of lines of code in a package (ideally ignoring comments, etc, such as sloccount) would be a helpful feature to determine whether a quick visual scan of the codebase is justified by the features offered. While lines of code are not a perfect indicator of code defects (apparently language tokens are a better fit) they are fairly accurate under common programming styles, and much easier to compute.
Other developers might chose to prefer high SLoC projects, as those hopefully solve rare bugs or implement features they'd find they need years later. With two valid and contrasting uses for the data, it should be useful to show.
The text was updated successfully, but these errors were encountered:
Similar to issue #32 - showing the number of lines of code in a package (ideally ignoring comments, etc, such as
sloccount
) would be a helpful feature to determine whether a quick visual scan of the codebase is justified by the features offered. While lines of code are not a perfect indicator of code defects (apparently language tokens are a better fit) they are fairly accurate under common programming styles, and much easier to compute.Other developers might chose to prefer high SLoC projects, as those hopefully solve rare bugs or implement features they'd find they need years later. With two valid and contrasting uses for the data, it should be useful to show.
The text was updated successfully, but these errors were encountered: