Remove nullable type-value and explicitly specify #77
Conversation
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
Removed null as an option for type-value because we explicitly specify nullable types starting with PR 75. Specified null as an option for capability-type-value and restricted-type-value. Added valid requirement for unique name in function-type.type-parameters. Thanks Bastian for suggesting this during our discussions on Slack and PR 75!
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.
We now explicitly specify nullable types starting with PR #75.
Remove null as an option for type-value.
Specify null as an option for capability-type-value and restricted-type-value.
Add valid requirement for unique name in function-type.type-parameters.
Thanks @turbolent for great suggestions during our discussions on Slack and for opening PR 75!
Closes #76