Skip to content

Stop tracking methods of classes with class types as signature - #108

Open
fantazio wants to merge 3 commits into
LexiFi:masterfrom
fantazio:cltyp
Open

fantazio wants to merge 3 commits into
LexiFi:masterfrom
fantazio:cltyp

Conversation

@fantazio

Copy link
Copy Markdown
Collaborator

Fix #107

According to the documentation, none of the methods declared via a class type should be tracked, regardless of their use.
It was the case for immediate objects but not for classes.

The documentation is updated to include an example of class with class type as signature.
DeadObj.collect_export is updated to fit the described semantics.

Some legacy tests that were expecting the wrong results are now fixed.

This PR also includes a fix in the documentation of the methods limitations. It was still including the example for the alias limitation, which has been fixed by #98.

NB: class types have a restriction similar to module types.

…ignatures

This is supposed to be the behavior according to the documentation and
some legacy tests were actually expecting the wrong results according
it.
The tests are now fixed to fit the described semantics and
`DeadObj.collect_export` too.

NB: class types have a restriction similar to module types.
Now it includes a class with a class type as signature, identical to the
immediate object with class type as signature
It was still including the example for the alias limitation, which has
been fixed by LexiFi#98.
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.

"unused methods" false-positives

1 participant