How important is the `@_dispatchable` decorator in networkx?

Can this decorator be removed?

One obvious advantage for having it is to mirror runtime. It has some disadvantages though:

1. I can't for the life of me find a way to use it on overloaded functions. Indeed looking at the stubs, overloaded functions are stripped of this decorator
2. VS Code with Pylance does not show the documentation of the function on hover only when the decorator is used

I find the overload case very important that it outweighs the benefits of matching runtime. I also think the editor hover issue compelling on its own but one could argue that this should be discussed with the Pylance team instead.

I wonder if we could just get rid of the decorator altogether. Am I missing other reasons for having the decorator?

Commencez par rechercher les utilisations du décorateur @_dispatchable dans typeshed et par les comparer aux fonctions surchargées dans les stubs. Examinez la justification de la mise en miroir de l’exécution ainsi que le comportement de survol de Pylance signalé. La tâche est terminée lorsqu’une décision a été prise quant au maintien du décorateur et que cette décision a été documentée ou implémentée.