pylint #9127 implement a function call diagram [open]

it would be interesting to have a function call diagram, to have a more precise idea of how a class or a module is working. For that we should usually infer each object, but maybe we can somehow work around by the fact that if:


and the only class having an "is_changing" method in our project is in the class "Something", than "anything" should be a Something instance (except monkey patching or things like that).

done in<not specified>
closed by<not specified>