fix(unexported-return): add missing TypeCheck call #1308
Merged
+3
−1
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.
This PR needs PR #1307.
The problem of consistency was related to a missing call to
Package.TypeCheck().The
UnexportedReturnRulecallsPackage.TypeOf(), but this requires the data fromPackage.TypeCheck(): depending on the order of the rule, the data may exist or may not.I checked the calls to
Package.TypeOf(), and it is only missing forunexported-return.The bad news is that
unexported-returnis now a part of the other issue aboutPackage.TypeCheck().Concretely, it was already a part of this issue as it relies on
Package.TypeOf().The regression comes from #1170 (v1.6.0); this explains why the number of issues has increased since the beginning of the year.
Note: I also fixed a problem with a missing call to
types.Unalias().Fixes #1306
Note: numbers have changed (723 -> 722) because I replaced
wcwithjq(so no extra empty line).revive-bench.sh