-
Notifications
You must be signed in to change notification settings - Fork 19
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
Simplify the parameter checks for overrides. #829
Conversation
DO NOT MERGE, probably. See discussion from about jspecify/jspecify-reference-checker#193 (comment) onward. This PR is a lazy way for me to run tests, since I don't trust myself to find the right way to run them all locally.
f1d50e8
to
85c2470
Compare
For the record, for cpovirk@85c2470 (
I might now test a variant of that. |
OK, I see the same problem if I merely pass |
...and the same problem if I put the I'm sure it could be interesting to dig deeper, but I'm just going to take away from this that there's no code that became trivially removable somewhere along the way. |
(#849 suggests that the errors I'm seeing may or may not actually have been caused by the changes I was testing. For my current purposes, that still means that the code is not "trivially removable." But maybe I'll revisit it someday, assuming my investigation in jspecify/jspecify#583 doesn't make the changes look like a non-starter.) |
OK, that version (which wasn't my original version) fails one test that seems potentially unrelated:
I'm going to see what happens with the original version. |
Thanks. It looks like the original version fails only in that similar way, so I think everything I've seen is still at least compatible with the idea that this code could be simplified. Anyway, I don't want to actively pick this up now; I just remembered seeing that the earlier CI failure had been fixed, so I figured I'd resurrect this PR for testing purposes. Whenever I get back to jspecify/jspecify-reference-checker#193, I may end up wanting to push this forward, or I might not. |
DO NOT MERGE, probably.
See discussion from about
jspecify/jspecify-reference-checker#193 (comment)
onward.
This PR is a lazy way for me to run tests, since I don't trust myself to
find the right way to run them all locally.