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.
it is very concerning that changing these directions (widening instead of narrowing) doesn't require changing any tests.
I should probably try to find some example that fails in the previous direction... I guess it is actually very rare for subsCheck to not be just unifying the code into a single type rather than instantiating.
Or it could be that we just don't have any way of failing after coerce since we just assume the types are right after that so changing them can't change the tests... but it seems like we should be able to find some code that didn't type before that does now?