Future type annotations #580
Merged
Conversation
This file contains 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
janosh
force-pushed
the
future-type-annos
branch
from
3a12d53 to
3401e29
Compare
janosh
force-pushed
the
future-type-annos
branch
from
3401e29 to
90b8d72
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #580 +/- ##
==========================================
+ Coverage 75.48% 75.49% +0.01%
==========================================
Files 80 80
Lines 6722 6725 +3
Branches 992 992
==========================================
+ Hits 5074 5077 +3
Misses 1342 1342
Partials 306 306
|
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.
Follow up to #578. Make sure we use future type annotation in all non-schema files and bump
rufftarget version to 3.9.