long-m-r / mydipy Goto Github PK

While this may partially work at present, I've had mixed success in current testing. Seems like there is a lot more to do here to make it robust.

If a method takes a string, integer, or any other type of class and we can cast the input arguments to that class, should we do this?

Requirements:

• Used as a fallback (we'd rather search the all overloads and match that before casting to match an earlier overload)
• Make it optional. Add another class parameter like auto_cast=<True|False> (default to False) and introduce a new @autocast decorator
• How to handle errors? I'm guessing we would ignore TypeErrors and TypeCheckErrors when evaluating.

Is this worth doing?

There are lots of types defined in https://docs.python.org/3/library/typing.html which may or may not be handled appropriately in MyDiPy. We'll need to test a lot of these and identify which ones to support.

From early testing, some seem to work well and others are a disaster.