-
Notifications
You must be signed in to change notification settings - Fork 94
Allow arbitrary number of arguments to submit #797
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
Conversation
Wait, hold on. Aren't there |
They will get an error like it's not supported: |
If you try to submit using a submittable that's supported, then you'll hit I don't see an easy workaround if we're following the
Is this an issue with the fallback or with the definition of |
Not, just with the fallback. |
Codecov Report
@@ Coverage Diff @@
## master #797 +/- ##
======================================
Coverage 94.1% 94.1%
======================================
Files 59 59
Lines 6671 6671
======================================
Hits 6278 6278
Misses 393 393
Continue to review full report at Codecov.
|
In fact, it does not make sense to throw |
What is preventing us from defining the fallback without using varargs? |
Nothing, let's open an issue #799 |
LGTM. Merge when ready. |
It would have zero argument for
RejectSolution
, see #782, it would be weird to require the user to provide atuple()