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

Guidelines about when to use Option with Qt return types #253

Open
Ayush1325 opened this issue Feb 26, 2022 · 0 comments
Open

Guidelines about when to use Option with Qt return types #253

Ayush1325 opened this issue Feb 26, 2022 · 0 comments

Comments

@Ayush1325
Copy link
Collaborator

I was writing a wrapper for a few functions in QStandardPaths which I need and a question popped up in my mind. Many Qt functions return a null QString (not to be confused with empty QString) when the value cannot be found. In such cases, should the bindings return Option<QString> instead of QString?

Similarly, most Qt functions will return empty QList when nothing is found. So I would like to hear everyone's opinions about using Option in the return type of such functions.

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

No branches or pull requests

1 participant