-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only support tuples and not single inputs/outputs #103
Comments
An alternative would be #53 |
Good point. How to decide between the two? Would one be
|
On second thought they're actually the same, replacing |
I think it should be fine to only support tuples. I don't recall why we support both but we can just support one. |
Only supporting plain inputs / outputs as in #53 sounds slightly more natural though, doesn't it? |
that's also fine by me |
Closing this in favor of #53 then |
The ambiguity between tuples and single inputs/outputs in pushforwards and pullbacks is causing several bugs (#99) and making the code more complicated.
I propose to make a breaking change that supports only tuples
cc @devmotion
The text was updated successfully, but these errors were encountered: