Unify requiredBacked and nullableBacked properties#4
Open
n0900 wants to merge 8 commits into
Open
Conversation
JesusMcCloud
left a comment
JesusMcCloud
left a comment
Contributor
There was a problem hiding this comment.
seems counterintuitive to enforce non-null types for nullables
Collaborator
Author
thats true but if we dont then |
n0900
force-pushed
the
feature/betterTypes
branch
from
f998621 to
9fa6c6b
Compare
n0900
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Asser that T: Any to allow kotlinx serialization to automatically define nullable serializer and guarantee that type is not nullable in the case non-nullable function is usedUnify the two backed property paths