Open DeathlessDogface opened 7 months ago
I'm torn on this one, as we have a pending design/implementation action for specifically choosen default values (for backward/forward compatibility of hook impl's/specs as parameters are added/removed
part of me wants to formally forbid default values other than None so they can specifically be used to manage addition/removal of parameters in specs/impls
I'm sorry, I just saw this reply. Now I understand the comments in the code, thank you. However, I would still like to recommend my changes to you again.
Fix the issue where passing keyword argumentss was not effective, and enhanced the test cases for the _multicall() function
The issue like this:
test code
test result