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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Type checkers part 2 #1391
Type checkers part 2 #1391
Changes from 10 commits
85352f2
e47a264
18305b5
d967fc1
d6ec95d
0e2843b
a636e59
6319106
1374a71
953f1c8
ae3d53c
784b041
68e54de
8af50d7
1404d01
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a lot of moving things here and in #1387. My rationale is that, if a the tuning process inserts a value, we would not check it. For example,
finalize_recipe()
does use the constructor.It does defer the checking until prep-time which is later than this but it seems like the only way to really be sure that we are getting corrrect inputs.