Repository navigation
Why does the argument order of pyconvert_add_rule deviate from convention #363
Description
Activity
No particular reason. It started life as a non-API function. I'll consider this for v1 - the pyconvert machinery is going to be overhauled anyway.
Feel free to make a PR to add a version with the function-first order.
According to the Julia Docs, function arguments should be placed first because "Putting a function argument first permits the use of do blocks for passing multiline anonymous functions."
Is there a reason for not following this convention?
Would it be reasonable to support the conventional argument order in addition to the current argument order?
Can we switch fully to the conventional argument order and deprecate the current argument order / remove it in the next breaking release?