[gtk] Default to trust_return_value_nullability #71
Conversation
This file contains 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
|
Makes it more obvious which ones still need to be taken care of, so I like it |
|
Sounds good to me, but let's wait until the regen with 2018 edition is in first. |
|
The regen with 2018 edition is now, this can now be rebased. It seems that the bindings were not re-generated btw |
|
The point of this PR is that nothing in the bindings changes at all. It's just a change in how we use |
|
Ah my bad. Didn't notice the global change of |
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.
Can we do it this way round? Here, every Object marked with
trust_return_value_nullability = falseshould be checked and fixed at some point.#68