Skip to content

Remove ReExcessiveMethodsRule - #19866

Open
jecisc wants to merge 1 commit into
pharo-project:Pharo15from
jecisc:misc/too-many-methods
Open

Remove ReExcessiveMethodsRule#19866
jecisc wants to merge 1 commit into
pharo-project:Pharo15from
jecisc:misc/too-many-methods

Conversation

@jecisc

@jecisc jecisc commented Jul 7, 2026

Copy link
Copy Markdown
Member

It seems that this rule is not good because smalltalk encourage to have small methods. But how can we have small methods if we are limited in the number of methods?

This seems to be the result of the discussion on this issue: #19815

So I'm proposing to remove this rule. I'm opening a PR to propose this change and now I'm letting the community comment about merging it or closing it depending on what we want

Fixes #19815

It seems that this rule is not good because smalltalk encourage to have small methods. But how can we have small methods if we are limited in the number of methods?

This seems to be the result of the discussion on this issue: pharo-project#19815

So I'm proposing to remove this rule. I'm opening a PR to propose this change and now I'm letting the community comment about merging it or closing it depending on what we want
@Ducasse

Ducasse commented Jul 31, 2026

Copy link
Copy Markdown
Member

What would be nice is to compute the average # of methods of the package and flag the 20% that are above that value. Because 60 is not a good idea.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

"Class has too many methods" rule could exclude test cases

2 participants