-
Notifications
You must be signed in to change notification settings - Fork 161
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
Change Test() to reject unexpected or invalid inputs #2519
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2519 +/- ##
==========================================
+ Coverage 74.41% 74.46% +0.04%
==========================================
Files 481 481
Lines 242659 245614 +2955
==========================================
+ Hits 180586 182907 +2321
- Misses 62073 62707 +634
|
I suggest we merge this, and then see if any packages fail |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree, that there is probably some proper error if this is triggered.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree. Cf. also #2524 which is somehow complementary to this.
This is a somewhat experimental change to fix #2506 -- let's see if the GAP test suite passes with it.
Assuming this works for the test suite, I wonder if there are any reasonable scenarios where the new
Error
call is triggered and where this is undesirable. If anybody knows such an example, please bring it up. In that case, we could add an option to turn off that error; or restrict the cases in which it is triggered.