Skip to content
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

component: Mark relevant return types as nullable #204

Merged
merged 1 commit into from Oct 10, 2018

Conversation

davidmhewitt
Copy link
Contributor

These types are not marked as nullable in the resulting GIR file and hence not marked nullable in any bindings downstream of that; for example, the Vala bindings.

Having these marked as nullable would allow more robust Vala code to be generated when these methods are used.

This only touches Component for now in case there's some reasoning behind why these haven't been marked nullable, but I'm happy to submit a PR to cover off the rest if this is wanted.

These types are not marked as nullable in the resulting GIR file and hence not marked nullable in any bindings downstream of that; for example, the Vala bindings.

Having these marked as nullable would allow more robust Vala code to be generated when these methods are used.

This only touches Component for now in case there's some reasoning behind why these haven't been marked `nullable`, but I'm happy to submit a PR to cover off the rest if this is wanted.
@ximion
Copy link
Owner

ximion commented Oct 10, 2018

Makes sense, I think when the code was written I didn't know that return values can be tagged as nullable as well.
Thank you for the patch!

@ximion ximion merged commit e40c71b into ximion:master Oct 10, 2018
@davidmhewitt davidmhewitt deleted the patch-1 branch October 10, 2018 11:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants