Repository navigation
Conversation
Some packages make checkers do different amounts of work, which the raw times don't show. Notes live in typecheck_benchmark/package_notes.json and appear as an info button after the package name in the Every Package table, with markers on the affected checkers' cells. All open one native popover. A missing or malformed notes file leaves the table as it was. First note: pydantic-core's CoreSchema is a large TypedDict union only when MYPY is false, so Mypy and Zuban check Mapping[str, Any] instead. The daily benchmark job and deploy.yml now publish the notes file.
Hovering or focusing an info button shows its note beside it; moving onto the note keeps it open so its source link can be clicked. A tap shows it on touch screens. Esc, clicking elsewhere or scrolling hides it.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses #162 by creating a tool to help explain caveat/explain where checking behavior will impact performance with an asterisk.