Skip to content

Conversation

@hauntsaninja
Copy link
Collaborator

Reverts #20696

@ilevkivskyi
Copy link
Member

Just curious, did this cause some problems?

@hauntsaninja
Copy link
Collaborator Author

Yes, the second PR did, see #20696 (comment)
I wasn't as careful as in the first PR

@github-actions
Copy link
Contributor

github-actions bot commented Feb 1, 2026

According to mypy_primer, this change doesn't affect type check results on a corpus of open source code. ✅

@ilevkivskyi
Copy link
Member

Hm, OK, I see. Maybe you can simply check if there any active error watchers (IIRC I already needed this for something, so I am quite this should be easy)? This should allow skipping a bunch more error-emitting code.

@hauntsaninja
Copy link
Collaborator Author

Will do!

@hauntsaninja
Copy link
Collaborator Author

hauntsaninja commented Feb 3, 2026

Merging this for now to keep master usable, will follow up with the watcher change + better testing

@hauntsaninja hauntsaninja merged commit 21eb6a1 into master Feb 3, 2026
23 checks passed
@hauntsaninja hauntsaninja deleted the revert-20696-perfcheck branch February 3, 2026 04:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants